agent-support

A vendor declares how AI agents can reach its support by serving a JSON document at:

https://<your-domain>/.well-known/agent-support

{
  "version": "0.1",
  "endpoint": "https://api.acme.com/mcp/support",
  "auth": "customer_api_key",
  "fallback_email": "support@acme.com",
  "contact_form": "https://acme.com/support/contact",
  "contact_platform": "intercom",
  "expected_response": "seconds"
}

Fields

Field	Required	Description
`version`	✓	Spec version. Currently `"0.1"`.
`endpoint`	one of ⊕	HTTPS URL of a live MCP endpoint answering agent questions in real time.
`fallback_email`	one of ⊕	Support email for asynchronous, well-formed tickets.
`contact_form`	one of ⊕	Public HTTPS support form an authorized browser agent may submit for the user.
`contact_platform`		Optional `intercom`, `zendesk`, or `generic` routing hint.
`auth`		`none` · `customer_api_key` · `oauth`. How agents authenticate to `endpoint`.
`expected_response`		`seconds` · `minutes` · `hours` · `business_days`, which lets agents decide whether to wait or park the task.
`docs`		URL of public docs agents should check first.

⊕ At least one of endpoint, fallback_email, or contact_form must be present. Unknown fields are permitted and ignored.

Minimal document: the zero-commitment step

No endpoint required. Publishing this alone improves how agent traffic reaches you:

{
  "version": "0.1",
  "fallback_email": "support@acme.com",
  "expected_response": "business_days"
}

Rules

Serve over HTTPS with Content-Type: application/json; cacheable, so clients cache up to 24 hours.
The well-known document is authoritative: clients must prefer it over any third-party directory entry for your domain.
Clients treat 404 as "not published" and fall back to other resolution.

Validate

npx askfirst-mcp check-vendor acme.com

Vendor-neutral by design: any implementation can serve the endpoint or consume this document. Maintained by AskFirst; JSON Schema and reference implementation ship with askfirst-mcp.