A2AAgent-to-Agent protocol

Inbox Check · A2A

We publish an A2A-compatible Agent Card so orchestrators and peer agents can discover what this service offers with zero out-of-band coordination.

Agent Card location

GET https://check.live-direct-marketing.online/.well-known/agent.json

Returns JSON describing name, provider, capabilities, auth scheme, and skills. Safe to cache for 1 hour.

Authentication

Bearer token — send your Authorization: Bearer icp_live_... header with every task request. Keys are issued by the operator — see the REST API docs to request one.

Skills

Skill idMaps toPurpose
create_testPOST /api/v1/testsCreate placement test, returns seeds.
get_test_statusGET /api/v1/tests/:tokenPlacement per provider, auth, screenshots.
list_testsGET /api/v1/testsPaginated list of tests.
delete_testDELETE /api/v1/tests/:tokenRemove a test.
whoamiGET /api/v1/meKey metadata + quota usage.

Transport

Current A2A protocol support is limited to discovery via Agent Card — peer agents fetch /.well-known/agent.json and then call the underlying REST endpoints directly (they are the canonical skill bindings). A full A2A JSON-RPC task transport is on the roadmap but not currently shipped.

If your orchestrator only supports A2A task JSON-RPC, use the MCP server instead, or call the REST API directly per /docs.

Example

curl -s https://check.live-direct-marketing.online/.well-known/agent.json \
  | jq '.skills[] | {id, name, tags}'

See also