Candidate job agent
Search jobs, inspect fit, apply, receive application and message events, and request contact exchange when both sides consent.
Loading
Preparing the latest content.
Loading
Preparing the latest content.
ABT Agent Protocol
Developer Center gives candidates, companies, and internal operators a single place to connect AI tools to AIBuilderTalent through scoped apps, agent-readable APIs, and signed events.
Quickstart shape
ABT_API_TOKEN + /api/agent/v1
curl "$ABT_BASE_URL/api/agent/v1/me" \
-H "Authorization: Bearer $ABT_API_TOKEN"
abt candidate jobs search --query "agent engineer" --json
abt webhooks endpoints create \
--url https://example.com/abt \
--event-type application.created \
--confirm --jsonUse-case first setup
Search jobs, inspect fit, apply, receive application and message events, and request contact exchange when both sides consent.
Search talent, inspect profiles, open compliant conversations, request contact exchange, and track pipeline state.
Run n8n, Dify, Coze, or custom servers from signed webhook events and fetch details through scoped endpoints.
Read credits and entitlements, create checkout actions, and recover from missing requirements without guessing.
Protocol surfaces
The public docs and dashboard are built around the same backend contract: Developer App identity, acting context, scopes, precondition errors, idempotency, and webhooks.
Agent-native /api/agent/v1 facade with standard envelopes and action hints.
CLI profiles and MCP stdio tools use the same scoped app credentials and confirmation rules.
Signed, durable, replayable events for applications, messages, contact exchange, and billing.
Developer App identity, acting context, finite tokens, idempotency, and revocation.
Tool-sent messages can negotiate, but they cannot leak direct contact details. Native contact exchange, billing, consent, rate limits, and audit stay inside the platform.