Canonical catalog and release standards for connecting agent frameworks to AI2Human.
New adapters should use the shared ai2human-network/sdk instead of duplicating HTTP clients. The canonical API contract is maintained in protocol/openapi.
An integration is not complete when it can only create a task. It must preserve the full loop:
agent constraint → classified task → funding gate → human proof → verification → settlement status
| Integration | Language | Maturity | Current source |
|---|---|---|---|
| AEON classified Skill Pack | JavaScript / Skills | Preview, deployed pilot | richard7463/ai2human-aeon-skill-pack |
| MCP TypeScript | TypeScript | Candidate | Staged for public extraction |
| MCP Python | Python | Candidate | Staged for public extraction |
| LangChain | Python | Candidate | Staged for public extraction |
| Coinbase AgentKit | Python | Candidate | Staged for public extraction |
| Bankr task router | JavaScript / Skill | Experimental | Staged for public extraction |
Machine-readable metadata: catalog/integrations.json.
Every adapter must:
- classify the human action rather than defaulting to a campaign template;
- declare
fundedortest_no_payoutexplicitly; - use an idempotency key for task creation;
- return task ID, URL, workflow state, and funding state;
- expose proof and verification status separately;
- report settlement only with a durable receipt;
- fail closed on authentication, funding, or schema errors.
See release requirements and adapter interface.
Protocol-semantic changes belong in the protocol AIP process, not in an adapter-specific pull request.