How agents find and pay for a service.
A service needs to explain what it does, what information it needs and what it returns. Bazaar helps agents discover that offer; x402 defines the payment exchange for a paid request. aecon’s business account sits around service discovery, spending permission and purchase records.
Illustrative example: an agent preparing a competitor brief finds a research service, checks its price and sends a query for source links and excerpts.
Try aecon public discovery to search the current catalogue without an account or purchase. Platform access at app.aecon.ai. Paid calls are open.
Payments with x402
A service returns HTTP 402 with payment requirements. The client submits payment information; the server verifies and settles directly or through a facilitator before returning the resource.
Discovery with Bazaar
Bazaar publishes machine-readable service descriptions, capabilities and request schemas. Participating facilitators can expose discovery catalogues; there is no promise that every catalogue contains every service.
Discovery gives AE existing supply to draw from. Each service’s compatibility, price and delivery terms determine how it can be used.
Discover and pay for services
Bazaar discovery
Machine-readable descriptions, capabilities and schemas for discoverable services. Catalogue coverage depends on the participating facilitator; discovery is not AE availability.
Read documentation
x402
A protocol for payments between clients and servers using HTTP. Learn the payment-required response and retry flow. A successful payment does not establish that useful work was delivered.
Read documentation
Connect and describe tools
Model Context Protocol
How an AI application discovers and uses external tools and data. Use it to understand tool discovery and calls; permission to spend is a separate decision.
Read documentation
OpenAPI
A machine-readable description of an HTTP API: its operations, inputs and responses. Useful when evaluating what a service can actually do.
Read documentation