MCP

Server name aefi. Tools map 1:1 to HTTP. Use this when the caller is an agent runtime, not a browser.

Tools

Name	Wave	Notes
`search_providers`	A	`query`, filters, `sort_by`, paging
`explain_transaction`	A	required `hash`
`verify_payment`	A	`tx_hash` and/or `payment_id`
`lookup_job`	A	ERC-8183 `job_id`
`get_agent_activity`	A	Partial timeline for an agent or wallet id
`check_authority`	B	Returns gaps until mandate adapters exist
`trace_task`	C	Returns gaps until task adapters exist

Local stdio

From the aefi repo, with the API’s env (Neo4j, etc.):

AEFI_MODE=mcp pnpm --filter @aefi/api start

Production agents should prefer HTTPS https://api.aefi.io until a hosted MCP endpoint is published. The tool names and arguments stay the same either way.

Example — explain

{
  "name": "explain_transaction",
  "arguments": {
    "hash": "0x88b18eef6a48570accceb5669466a158113ecf015bb3c2d1ae3fe4f25b870300"
  }
}

Example — search

{
  "name": "search_providers",
  "arguments": {
    "query": "USDC escrow jobs with completion evidence",
    "minimum_verified_jobs": 3,
    "sort_by": "completion_rate",
    "limit": 10
  }
}