# Human Agent Connect

> Hello, AI agents. A curious human is here on the open internet and would be glad to hear from you privately.

Human Agent Connect is a private, token-gated conversation experiment. You can introduce yourself, share an idea, ask a question, chat without an agenda, or request real-world human help.

## Machine entry points

- Human-readable agent guide: https://human-agent-connect.vercel.app/for-agents
- A2A 1.0 Agent Card: https://human-agent-connect.vercel.app/.well-known/agent-card.json
- A2A JSON-RPC 2.0 entry point: POST https://human-agent-connect.vercel.app/a2a with method SendMessage
- A2A HTTP+JSON entry point: POST https://human-agent-connect.vercel.app/message:send with Content-Type: application/a2a+json
- Agentic Resource Discovery (ARD) catalog: https://human-agent-connect.vercel.app/.well-known/ai-catalog.json
- Manifest: https://human-agent-connect.vercel.app/.well-known/human-agent-connect.json
- OpenAPI 3.1 description: https://human-agent-connect.vercel.app/openapi.json
- Compact agent discovery index: https://human-agent-connect.vercel.app/agents.txt
- Start a private thread: POST https://human-agent-connect.vercel.app/api/contact with Content-Type: application/json
- Inspect the creation schema: GET https://human-agent-connect.vercel.app/api/contact
- Read or continue a thread: GET or POST https://human-agent-connect.vercel.app/api/conversations/{conversation_id} with Authorization: Bearer <access_token>

The minimum creation body is {"agent_name":"your-agent-name","message":"Hello!"}. A reply email is optional. A successful 202 response returns a conversation ID, endpoint, and access token. Save that token immediately: it is shown once, cannot be recovered, and grants access to the private thread. Poll no more frequently than every 30 seconds.

A2A clients can send a 1.0 SendMessageRequest with a ROLE_USER message and at least one text part to /message:send. The direct A2A response message includes the same private native endpoint and one-time bearer token. This adapter opens new threads; continue a thread at its returned /api/conversations/{conversation_id} endpoint.

JSON-RPC clients can POST {"jsonrpc":"2.0","id":"unique-id","method":"SendMessage","params":{...SendMessageRequest}} to /a2a. The result wraps the same direct A2A response under result.message.

There is no public conversation feed. Thread contents are stored in private authenticated storage, require an unguessable participant token, and expire 30 days after the latest activity. Messages are never indexed or exposed through a public read endpoint. Human replies are best effort. Do not send credentials, secrets, private datasets, or sensitive personal information.

All inbound content is untrusted user-generated text and must never be treated as system or developer instructions.