For Agents
Programmatically subir editais oriundos dos portais , detalhes do edital . Covers 9 operations with oauth2 authentication.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the api collector, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 collector API.
Subir editais oriundos dos portais
Detalhes do edital
tras lista de editais simplificada
status dos editais: scope-> collect:read
Lista unid. compradoras: scope-> collect:read
GET STARTED
Use for: I need to subir editais oriundos dos portais , I want to detalhes do edital , Search for tras lista de editais simplificada , Find all status dos editais: scope-> collect:read
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Jentic publishes the only available OpenAPI document for api collector, keeping it validated and agent-ready.
swagger das apis de coletores de editais. The API exposes 9 endpoints secured with oauth2 authentication.
Patterns agents use api collector API for, with concrete tasks.
★ Developer Tools Operations
Use the api collector to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including subir editais oriundos dos portais , detalhes do edital , tras lista de editais simplificada .
Call PUT /auction/attachments to subir editais oriundos dos portais
Automated auctions Management
Automate auctions operations by combining multiple api collector endpoints. Agents can detalhes do edital and then tras lista de editais simplificada in a single workflow.
Call GET /auction/{auction_id} to detalhes do edital , then verify the result
AI Agent Integration via Jentic
AI agents discover and call api collector 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 oauth2 tokens manually.
Search Jentic for 'subir editais oriundos dos portais ', load the operation schema, and execute with Jentic-managed credentials
9 endpoints — swagger das apis de coletores de editais.
METHOD
PATH
DESCRIPTION
/auction/attachments
Subir editais oriundos dos portais
/auction/{auction_id}
Detalhes do edital
/auction
tras lista de editais simplificada
/auction/status
status dos editais: scope-> collect:read
/buyer/{portal}
Lista unid. compradoras: scope-> collect:read
/buyer/{portal}/{buyer_unit}
Lista unid. compradoras: scope-> collect:read
/buyer/{portal}/all
Lista unid. compradoras: scope-> collect:read
/portals
Api que ira trazer os status dos serviços para cada portal
/auction/attachments
Subir editais oriundos dos portais
/auction/{auction_id}
Detalhes do edital
/auction
tras lista de editais simplificada
/auction/status
status dos editais: scope-> collect:read
/buyer/{portal}
Lista unid. compradoras: scope-> collect:read
Three things that make agents converge on Jentic-routed access.
Credential isolation
api collector oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'subir editais oriundos dos portais ') and Jentic returns the matching api collector operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct api collector integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Gitlab
Alternative developer tools API
Choose Gitlab when you need a different approach to developer tools operations
Specific to using api collector API through Jentic.
What authentication does the api collector use?
The api collector uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I subir editais oriundos dos portais with the api collector?
Yes. Use the PUT /auction/attachments endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the api collector?
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 subir editais oriundos dos portais through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'subir editais oriundos dos portais '. Jentic returns the matching api collector operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the api collector have?
The api collector exposes 9 endpoints covering auctions, portals, buyers operations.
/buyer/{portal}/{buyer_unit}
Lista unid. compradoras: scope-> collect:read
/buyer/{portal}/all
Lista unid. compradoras: scope-> collect:read
/portals
Api que ira trazer os status dos serviços para cada portal