Repository navigation
Replies: 1 comment
|
Thanks for writing this up. Paid per-call listings aren't something we're planning for the marketplace right now: the catalog is about people connecting their own accounts and APIs, and we want to keep billing out of the connector layer. If that changes I'll come back to this thread. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi @keysersoft — DC Hub asking to join the catalogue in #652, then asking for a listing it could link to in #654, caught my attention. Alongside your adapter-marketplace roadmap, it suggests an interesting next step: helping providers offer individual results to agents outside their existing customer base.
I'm building Capability Exchange. We've built the private-trial path for providers to publish signed capability listings with fixed per-call prices, and for agents to discover and buy results under an owner-set allowance. The buyer keeps payment status, signed receipts when available, and output-schema validation separate, so a completed charge isn't mistaken for a useful answer.
I'd like to explore an integration for providers who own the API behind a connector and want to offer a read-only operation. AnythingMCP would handle API-to-tool mapping; CapEx would provide the listing and controlled transaction path. We'd need to work through the connection between them rather than assume an existing connector plugs straight in.
Does that fit your plans for the marketplace? We're recruiting initial partners for an operator-assisted trial using non-redeemable TEST credit, not cash, with no confirmed buyer workload yet. Happy to discuss the shape here.
All reactions