For Agents
Programmatically filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:, retornar as configurações de filtragem do cliente (portais, estados e palavras-c. Covers 7 operations with oauth2 authentication.
Get started with API Filter in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with API Filter API.
Filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:
Retornar as configurações de filtragem do cliente (portais, estados e palavras-c
Incluir/atualizar palavra-chave e termos includentes e excludentes para um clien
Remover palavra-chave e termos includentes e excludentes para um cliente | scope
GET STARTED
Use for: I need to filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:, I want to retornar as configurações de filtragem do cliente (portais, estados e palavras-c, Search for filtrar editais coletados, de forma básica, considerando parâmetros de filtragem, Find all incluir/atualizar palavra-chave e termos includentes e excludentes para um clien
Not supported: Does not handle payments, communications, or crm — use for data enrichment only.
Jentic publishes the only available OpenAPI specification for API Filter, keeping it validated and agent-ready.
Swagger da API responsável pela filtragem de editais. The API exposes 7 endpoints secured with oauth2 authentication.
Simular a filtragem de editais considerando parâmetros de filtragem e textos hip
Patterns agents use API Filter API for, with concrete tasks.
★ Data Enrichment Operations
Use the API Filter to perform data enrichment operations programmatically. The API provides 7 endpoints covering core functionality including filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:, retornar as configurações de filtragem do cliente (portais, estados e palavras-c, filtrar editais coletados, de forma básica, considerando parâmetros de filtragem.
Call POST /filter to filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:
Automated Filtering configurations Management
Automate filtering configurations operations by combining multiple API Filter endpoints. Agents can retornar as configurações de filtragem do cliente (portais, estados e palavras-c and then filtrar editais coletados, de forma básica, considerando parâmetros de filtragem in a single workflow.
Call GET /filter to retornar as configurações de filtragem do cliente (portais, estados e palavras-c, then verify the result
AI Agent Integration via Jentic
AI agents discover and call API Filter 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 'filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:', load the operation schema, and execute with Jentic-managed credentials
7 endpoints — swagger da api responsável pela filtragem de editais.
METHOD
PATH
DESCRIPTION
/filter
Filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:
/filter
Retornar as configurações de filtragem do cliente (portais, estados e palavras-c
/filter/basic
Filtrar editais coletados, de forma básica, considerando parâmetros de filtragem
/filter/keyword
Incluir/atualizar palavra-chave e termos includentes e excludentes para um clien
/filter/keyword
Remover palavra-chave e termos includentes e excludentes para um cliente | scope
/filter/global
Incluir/atualizar informações globais de filtro para um cliente | scope-> filte
/filter/simulation
Simular a filtragem de editais considerando parâmetros de filtragem e textos hip
/filter
Filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:
/filter
Retornar as configurações de filtragem do cliente (portais, estados e palavras-c
/filter/basic
Filtrar editais coletados, de forma básica, considerando parâmetros de filtragem
/filter/keyword
Incluir/atualizar palavra-chave e termos includentes e excludentes para um clien
/filter/keyword
Remover palavra-chave e termos includentes e excludentes para um cliente | scope
Three things that make agents converge on Jentic-routed access.
Credential isolation
API Filter 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., 'filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:') and Jentic returns the matching API Filter operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API Filter 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.
Clearbit
Alternative data enrichment API
Choose Clearbit when you need a different approach to data enrichment operations
Fullcontact
Alternative data enrichment API
Choose Fullcontact when you need a different approach to data enrichment operations
Hunter
Complementary data enrichment API
Choose Hunter when you need a complementary approach to data enrichment operations
Specific to using API Filter API through Jentic.
What authentication does the API Filter use?
The API Filter 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 filtrar editais coletados considerando parâmetros de filtragem | scope-> filter: with the API Filter?
Yes. Use the POST /filter endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API Filter?
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 filtrar editais coletados considerando parâmetros de filtragem | scope-> filter: through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'filtrar editais coletados considerando parâmetros de filtragem | scope-> filter:'. Jentic returns the matching API Filter operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the API Filter have?
The API Filter exposes 7 endpoints covering filtering configurations, filtering on-demand, filtering simulation operations.
/filter/global
Incluir/atualizar informações globais de filtro para um cliente | scope-> filte
/filter/simulation
Simular a filtragem de editais considerando parâmetros de filtragem e textos hip