Agent-ready OpenAPI document · curated by JenticCRMDeal PipelineapiKey21 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read and write organizations, people, deals, tasks, and users in the Agendor Brazilian CRM via a focused 21-endpoint surface.
Use for: I need to list all open deals in Agendor, Find a person by CPF, Create a follow-up task for a specific user, Get the organization linked to a deal
Not supported: Does not handle product catalog management, account configuration, marketing campaigns, or invoicing - use for core Brazilian CRM pipeline operations on organizations, people, deals, and tasks only.
Jentic publishes the only available OpenAPI specification for Agendor API, keeping it validated and agent-ready. This 21-endpoint variant focuses on the core sales-pipeline objects in the Agendor Brazilian CRM: organizations, people, deals, tasks, and users. It targets the same v3 base URL but trims out the product catalog and account-configuration endpoints, which keeps the surface tight for integrations that only need to read and write the pipeline itself.
Install Jentic One Beta
Connect the Agendor API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agendor API, 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.
1
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%2Fagendor.com.br%2Fagendor-agendor-api" | sh2
Step 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%2Fagendor.com.br%2Fagendor-agendor-api" | 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.
Capabilities
What an agent can do with Agendor API.
List, retrieve, and update organizations identified by CNPJ
Manage people records with CPF and Brazilian address fields
Read and update deals across the sales pipeline
Create, list, and complete tasks for sales reps
Look up Agendor users to assign records and tasks
Filter deals by owner and date range for forecasting
Use Cases
Patterns agents use Agendor API for, with concrete tasks.
★ Sales Pipeline Sync
External sales tools pull Agendor pipeline data via GET /deals on a schedule and push status changes back to keep the CRM authoritative. The 21-endpoint surface is ideal for this - it gives full read/write to organizations, people, deals, and tasks without exposing endpoints the integration does not need.
List all deals via GET /deals modified in the last 24 hours and push the diff into the analytics warehouse
WhatsApp Sales Assistant
Brazilian sales teams that operate inside WhatsApp build assistants that read deal and contact context from Agendor before responding to a prospect. The assistant resolves a phone number to a person via /people, looks up the linked organization by CNPJ via /organizations, and returns deal status from /deals - all without leaving WhatsApp.
Given a prospect's phone number, find the matching person via GET /people, fetch their organization, and return the most recent open deal status
Task Reminder Bot
Reminder bots use the tasks endpoints to read overdue tasks and ping reps on Slack or WhatsApp. Each morning the bot pulls GET /tasks filtered by owner and due date, then sends individual reminders so the rep does not need to log into Agendor to triage their day.
Each morning, list overdue tasks per owner via GET /tasks and send a Slack DM to each rep listing the tasks past due
AI Agent CRM Operations
Through Jentic, an agent can read and update Agendor pipeline objects without holding the customer's API token. Jentic injects the Authorization header at execution time and the agent works with the structured response - ideal for embedded copilots in Brazilian sales tools.
Search Jentic for 'find organization by cnpj agendor', load the GET /organizations schema, and execute with the CNPJ filter
Key Endpoints
21 endpoints — jentic publishes the only available openapi specification for agendor api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/organizations
List organizations
GET
/organizations/{id}
Retrieve a specific organization
GET
/people
List people
GET
/people/{id}
Retrieve a specific person
GET
/deals
List deals
GET
/deals/{id}
Retrieve a specific deal
GET
/tasks
List tasks
GET
/organizations
List organizations
GET
/organizations/{id}
Retrieve a specific organization
GET
/people
List people
GET
/people/{id}
Retrieve a specific person
GET
/deals
List deals
GET
/deals/{id}
Retrieve a specific deal
GET
/tasks
List tasks
Jentic AI Readiness Score
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.
A
Agendor API
- AI-Aware (B+)68/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
33%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
70%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Agendor API by hand means managing its token in the Authorization header and coding calls across organizations, people, deals, and tasks. Through Jentic you install once, import the Agendor API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Agendor puts the resource id in the URL path for reads (/deals/{id}, /people/{id}), and every operation on this surface is a read, so a rule can pin the agent to reading a specific record. You choose which read operations are in the allowed set, so anything you leave out is not reachable.
Credential isolation
Your Agendor API token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Agendor deals', and Jentic returns the matching Agendor operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Payments platform used to charge customers once deals close.
Pair to charge a Stripe customer when an Agendor deal moves to 'Ganha'.
FAQs
Specific to using Agendor API through Jentic.
Why is there no official OpenAPI spec for Agendor API?
Agendor does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Agendor API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Agendor API use?
Agendor uses an API token in the Authorization header. Through Jentic, the token is stored encrypted in the vault and injected per call so the agent never holds it directly.
Can I find an organization by CNPJ with this API?
Yes. GET /organizations supports filtering, and GET /organizations/{id} returns the full record. CNPJ is one of the natural identifiers Agendor uses for Brazilian companies.
What are the rate limits for the Agendor API?
The public spec does not include explicit limits. Agendor throttles per account in practice - keep sync jobs to a few requests per second and back off on HTTP 429.
How do I list deals through Jentic?
Search Jentic for 'list agendor deals', load the GET /deals schema, and execute with whatever filters (owner, status) the agent needs. Jentic returns the deal list directly to the agent.
How does this differ from the other Agendor spec on Jentic?
This spec is the focused 21-endpoint pipeline surface. The 'agendor' spec is the broader 30-endpoint version that also covers products and account configuration. Use this one for tight integrations that only need pipeline objects.
Can I limit what my agent is allowed to do with the Agendor API?
Yes. Because you run Jentic One yourself, your own rules decide which Agendor operations and credentials the agent may use, and you pick exactly which read operations sit in the allowed set. Every operation on this surface is a read, and the resource id lives in the URL path for calls like GET /deals/{id} and GET /people/{id}, so a rule can pin the agent to reading a specific record such as one deal or one person. Anything you leave out of the allowed set, whether that is listing organizations, reading tasks, or looking up users, is not reachable by the agent.
GET STARTED