Endpoint states
| State | What it means |
|---|---|
| Drafted | An endpoint YAML file exists in the workspace. |
| Active draft | The endpoint file has active: true. It is eligible to publish. |
| Live | The active draft has been published into a runtime listing. |
| Inactive draft | The endpoint file has active: false. It stays private and unpublished. |
Publishing
Publishing applies active workspace endpoint files to live runtime records. It is the step that makes an endpoint callable through the platform. Before publishing, make sure:- Stripe Connect is complete.
- The endpoint has a valid price.
- Required upstream secrets are saved through secure secret fields.
- Validation has no blocking errors.
- The endpoint file is marked
active: true.
Distribution
Each live endpoint can expose several distribution surfaces:- public catalog listing
- MCP search result
- mirrored x402 URL
- normalized x402 run URL
- AgentCard URL
- Bazaar resource discovery status
Bazaar and first settlement
Bazaar-style discovery is tracked by x402 resource URL, not bypayTo. Agent Wonderland may use dynamic Stripe crypto PaymentIntent deposit addresses, so provider-level grouping by payTo should not be promised.
A resource may need successful settlement activity before external discovery systems index it. Agent Wonderland shows Bazaar status as a diagnostic, including whether a resource needs first settlement, has settlement observed, is indexed, or was not found.
Endpoint detail drawer
Open an endpoint row to inspect:- draft and runtime status
- method and path
- price
- distribution URLs
- Bazaar status
- recent failures
- 24 hour requests, success rate, latency, and revenue
- a link to the YAML file in Files