Agent API and MCP
Adrata exposes customer-gated tools for revenue agents: intro paths, buyer groups, company research, people enrichment, pipeline scoring, outreach, meetings, and workspace memory. Public docs explain the contract. Real data requires an authenticated Adrata workspace.
Customer-gated
API keys and OAuth scopes decide exactly which workspace data and actions an agent can use.
Event-driven
Agents should react to changes through webhooks and async jobs, not poll until something breaks.
Audited
Every read, write, enrichment call, and outbound action carries provenance, owner, and budget controls.
Run the MCP server anywhere your agent works.
Use MCP when the agent environment supports tools directly. Use the REST API when you need server-side control, webhooks, or product integrations.
$ npx @adrata/mcp-serverADRATA_API_KEY=ak_xxxxxxxxxxxxxxxxxxxx
ADRATA_API_URL=https://api.adrata.com/api/v1Tool families
24 primary tools grouped by the way sellers actually work. Intro groups come first because access opens the deal.
Intro Groups
Buyer Groups
Companies and People
Pipeline and Coaching
Outreach and Meetings
Research and Memory
Agentic API standard
A world-class agent API is not just request-response. It is safe under retries, event-driven when state changes, scoped by default, transparent about limits, and machine-readable for orchestration. This is the bar Adrata holds integrations and first-party tools to.
API design
Versioned REST contracts, OpenAPI, cursor pagination, and detailed error objects.
Events and streaming
Webhooks for state changes, signed events, retries, idempotent event IDs, and streaming where the agent needs live output.
Auth and security
Granular OAuth scopes, workspace API keys, rotation, least privilege, and audit logs.
Rate limits
Transparent rate-limit headers, burst behavior, backoff guidance, and credit-aware automation.
SDKs and docs
Machine-readable spec, examples, sandbox behavior, and agent-pattern guides.
Agent readiness
Idempotency keys, batch operations, async jobs, status polling, and safe retries.
Need direct API control?
MCP and REST use the same permission model, rate-limit headers, request IDs, idempotency behavior, and workspace audit logs.