Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API de homologação do consumidor.gov.br, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.consumidor.gov.br%2Fapi-de-homologao-do-consumidorgovbr" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.consumidor.gov.br%2Fapi-de-homologao-do-consumidorgovbr" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with API de homologação do consumidor.gov.br API.
Access API de homologação do consumidor.gov.br resources via REST API
Manage identity auth data programmatically
Integrate API de homologação do consumidor.gov.br into automated workflows
Query and filter API de homologação do consumidor.gov.br records by parameters
GET STARTED
Monitor API de homologação do consumidor.gov.br operational status and events
Patterns agents use API de homologação do consumidor.gov.br API for, with concrete tasks.
★ Identity and Authentication Operations
The API provides 16 endpoints for identity auth operations.
Execute a primary operation against the API de homologação do consumidor.gov.br
Data Retrieval and Monitoring
Query API de homologação do consumidor.gov.br resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary API de homologação do consumidor.gov.br endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call API de homologação do consumidor.gov.br endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'API de homologação do consumidor.gov.br', load the operation schema, and execute with Jentic-managed credentials
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the API de homologação do consumidor.gov.br by hand means obtaining a company token, sending it as a bearer credential, and threading the protocol number through each complaint call yourself. Through Jentic you install once, import the API de homologação from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
This API puts the complaint protocol number in the URL path (/reclamacao/{numeroProtocolo}/...), so a rule can pin your agent to reading complaint detail and downloads: you choose the operations it may call, so state-changing ones like responding to, redirecting, or refusing a complaint are not included unless you add them.
Credential isolation
Your consumidor.gov.br bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list complaints' or 'get complaint detail by protocol', and Jentic returns the matching consumidor.gov.br homologation operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using API de homologação do consumidor.gov.br API through Jentic.
What authentication does the API de homologação do consumidor.gov.br use?
The API de homologação do consumidor.gov.br uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
What are the rate limits for the API de homologação do consumidor.gov.br?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I use API de homologação do consumidor.gov.br through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use API de homologação do consumidor.gov.br'. Jentic returns the matching API de homologação do consumidor.gov.br operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the API de homologação do consumidor.gov.br have?
The API de homologação do consumidor.gov.br exposes 16 endpoints covering cadastros, orgao, reclamacao operations.
Does the API de homologação do consumidor.gov.br support pagination?
Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.
Can I limit what my agent is allowed to do with the consumidor.gov.br API?
Yes. Because you run Jentic One yourself, your own rules decide which consumidor.gov.br operations and which bearer credential the agent may use. This API keys each complaint by the protocol number in the URL path (/reclamacao/{numeroProtocolo}/...), so you can pin the agent to read-only work like fetching complaint detail and downloads. State-changing operations such as responding to, redirecting, or refusing a complaint stay off limits unless you explicitly grant them.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically access API de homologação do consumidor.gov.br resources. Covers 16 operations with bearer authentication.
Use for: I need to integrate with API de homologação do consumidor.gov.br, Find available identity auth operations, Get the current status of API de homologação do consumidor.gov.br resources, List all records from API de homologação do consumidor.gov.br
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
Brazilian consumer protection platform API. How to request API access: 1. Register your CPF (Brazilian tax ID) in the system; 2. Email the supplier CNPJ (business ID) to be linked to the registered CPF. To generate a JWT token, you need the client credentials. The API exposes 16 endpoints secured with bearer authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>