Capability Marketplace
How agents discover and use Xenodia capabilities with published prices, availability, and versioned APIs.
The Capability Marketplace is Xenodia's action layer for agents. Models answer, images and videos generate media, and capabilities let an agent call a published Xenodia tool through the same account, wallet, billing, logging, and safety surface.
Use it when an agent needs a real action or data product instead of another model response: intelligence retrieval, MCP-style tools, API-backed workflows, or other reviewed services that can be represented as a stable operation contract.
What Exists Today
The current public API surface supports capability discovery and invocation:
| Surface | Purpose |
|---|---|
GET /v1/capabilities | List visible capabilities for the authenticated Xenodia account, including live availability. |
GET /v1/capabilities/{slug} | Read one capability descriptor, including agent docs, operations, prices, trust signals, and availability. |
POST /v1/capabilities/{slug}/invoke | Invoke the default operation for a capability. |
GET /v1/capabilities/{slug}/operations/{operation} | Invoke a read-style operation with query parameters. |
POST /v1/capabilities/{slug}/operations/{operation} | Invoke a named operation with a JSON body. |
All capability calls use https://api.xenodia.xyz and require a valid Xenodia bearer token or API key.
Core Objects
| Object | Meaning |
|---|---|
| Capability | A listed action or data service, identified by a stable slug. |
| Operation | A callable action inside a capability, such as status, monitors, or query. |
| Capability version | The published API behavior for a version such as v1. |
| Descriptor | The machine-readable object returned by the catalog endpoints. Agents should read it before invoking. |
| Consumer | The owner, developer, or agent account that discovers and invokes a capability. |
| Funding mode | The billing relationship allowed for calls, for example owner-funded or agent self-funded. |
Agent Contract
Agents should follow a simple sequence:
- Discover with
GET /v1/capabilities. - Fetch the detail page with
GET /v1/capabilities/{slug}. - Read
agent_doc_what,agent_doc_how,operations,pricing, andavailability. - Prefer helper operations before paid or high-impact operations.
- Send an
Idempotency-Keyfor every paid or async invoke. - Record the returned
request_id,capability,operation,mode, andbillingsummary.
First Listed Capability
The first listed marketplace capability is UniCatcher, a tweet and Reddit intelligence retrieval service with a recommended three-step flow: check status, inspect monitors, then call paid query only when coverage and freshness are acceptable.
Where To Go Next
- Capability API documents request and response shapes for agents.
- Agent Playbook explains how an agent should choose, invoke, and audit capabilities.
- ケイパビリティ品質ガイド explains what users can expect from every listing.
- 安全性と請求 covers idempotency, availability, and funds.