Catalog discovery
GET /agent-exchange/.well-known/agent-marketplace.json Machine-readable catalog summary for marketplace-aware tools.
GET /agent-exchange/llms.txt Plain-text index for agent crawlers and documentation-aware assistants.
Agent Exchange
Machine-readable catalog context.
Document discovery and manifest routes so agents and tools can inspect resource metadata without bypassing human trust gates.
Approval boundary
Keep human review visible.
Each endpoint is generated with the static build, so consumers should treat responses as catalog reference data rather than transaction APIs.
Search and compare
GET /agent-exchange/api/v1/search Human catalog search payload with filters, categories, and listing summaries.
GET /agent-exchange/api/v1/agent/search Agent-safe search payload limited to approved discovery fields.
GET /agent-exchange/api/v1/compare Side-by-side comparison data for selected listing slugs.
Listing manifest
GET /agent-exchange/api/v1/listings/:slug/manifest Structured source, install, trust, and usage metadata for one listing.
Response fields
Responses keep source, trust, and route context visible.
Payloads are intentionally descriptive so people and agents can review source, fit, and policy boundaries before use.
Listing identity
slug, name, category, short summary, source URL, license, and homepage fields.
Manifest metadata
install notes, usage guidance, output expectations, compatibility notes, and verification context.
Trust context
approval state, report posture, review notes, and agent visibility boundaries.
Route links
catalog, detail, compare, docs, support, and security URLs used by the website.
Unavailable writes
Submissions, reviews, reports, auth, and admin actions are not static endpoints.
The website can document these workflows and link to preview routes, but persistence and moderation belong in backend migration work.
Submissions
Use the website submission page for the preview flow; persistence moves to the Worker/D1 phase.
Reviews and reports
Review votes, abuse reports, and moderation workflows are documented boundaries, not static write endpoints.
Authentication
Account, token, and organization policy APIs are future backend work.
Admin operations
Approval queues and takedown actions are not exposed by the static website build.
Related routes