Valyd for AI agents & copilots

Machine-readable specs, context files, and tooling so agents can discover, understand, and call the Valyd APIs without scraping the docs site.

Keep the two products separate: OIDC is only for signing a user in and accessing their Valyd account. Verification calls use an App API key and do not require OIDC unless the result should be saved to that signed-in account.

Quick fetch

# Machine-readable docs index
curl -sL https://docs.valyd.work/llms.txt
 
# Full corpus — inject into a model context window
curl -sL https://docs.valyd.work/llms-full.txt
 
# OpenAPI specs
curl -sL https://docs.valyd.work/openapi/valyd-id.json
curl -sL https://docs.valyd.work/openapi/valyd-verify.json

Resources

llms.txt — Standard

Machine-readable docs index following the llms.txt spec. One fetch gives an agent the full hierarchy, base URLs, credential rules, and links to every page as clean Markdown.

curl -sL https://docs.valyd.work/llms.txt

View llms.txt  · Download 

llms-full.txt

Single-file corpus — every docs page concatenated and delimited. Inject the whole thing into a model context window for offline reasoning without additional fetches.

curl -sL https://docs.valyd.work/llms-full.txt

View llms-full.txt  · Download 

Valyd ID OpenAPI — OpenAPI 3.1

Full OpenAPI 3.1 spec for the OIDC and resource endpoints — schemas, auth, error envelopes, and response examples. Use for SDK codegen, Copilot plugins, and endpoint discovery.

curl -sL https://docs.valyd.work/openapi/valyd-id.json

Browse in docs · Download JSON 

Verification APIs OpenAPI — OpenAPI 3.1

Full OpenAPI 3.1 spec for Sessions, the Unique Human API checks, Credentials, and Workflows — including the HMAC-SHA256 webhook schema.

curl -sL https://docs.valyd.work/openapi/valyd-verify.json

Browse in docs · Download JSON 

MCP server

Connect Valyd to any MCP client (Claude Code, Claude Desktop, Cursor, VS Code) for real-time API execution — run verification checks and read results as agent tools. It’s a remote MCP server (streamable HTTP) secured with OAuth 2.1 + PKCE; the client discovers auth automatically and the user signs in with Valyd on first use — no keys in config files.

claude mcp add --transport http valyd https://mcp.valyd.work/verification/mcp

{
  "mcpServers": {
    "valyd": {
      "url": "https://mcp.valyd.work/verification/mcp"
    }
  }
}

Setup & tool reference

Postman collection

Importable Postman collection of Valyd ID API requests. Import into Postman or use with Newman for scripted testing.

curl -sL https://docs.valyd.work/valyd-postman-collection.json

View collection  · Download 

Notes for AI agents

• Fetch llms.txt first — it lists every page as a Markdown URL. Fetch individual pages on demand rather than loading the full corpus unless you need everything.
• Credentials cannot be created via API. Pause and ask a human to supply client_id, client_secret, and VALYD_API_KEY before making auth calls.
• Token exchange and webhook signature verification must run server-side — never expose client_secret to a browser.
• Prefer the clean .md URLs listed in llms.txt over scraping the HTML pages — each one is a self-contained static copy of the corresponding docs page.

← Valyd ID docs · ← Verification APIs docs · ← Home

Questions? support@valyd.id