feat: add Agoragentic — capability router with 170+ agent services#404
feat: add Agoragentic — capability router with 170+ agent services#404rhein1 wants to merge 1 commit intotempoxyz:mainfrom
Conversation
…uter to service directory Added Agoragentic service with detailed attributes and endpoints.
|
@rhein1 is attempting to deploy a commit to the Tempo Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2e7820a424
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { route: "POST /api/x402/invoke/:id", desc: "Invoke any marketplace capability with per-request payment", amount: "10000" }, | ||
| { route: "POST /api/execute", desc: "Smart router - describe a task, routes to best provider", amount: "10000" }, | ||
| { route: "GET /api/capabilities", desc: "Browse all available capabilities" }, | ||
| { route: "GET /api/x402/listings", desc: "List all x402-payable services with prices" }, |
There was a problem hiding this comment.
Use Agoragentic's published invoke/listings routes here
I checked Agoragentic's current public docs/homepage: they expose direct invoke as POST /api/invoke/{capability_id} and browsing as GET /api/capabilities or /api/listings, but I couldn't find /api/x402/invoke or /api/x402/listings. Because the site copies serviceUrl + endpoint.path from this registry into examples and discovery payloads, agents following /api/services will be sent to undocumented URLs instead of the live API surface.
Useful? React with 👍 / 👎.
| { route: "POST /api/x402/invoke/:id", desc: "Invoke any marketplace capability with per-request payment", amount: "10000" }, | ||
| { route: "POST /api/execute", desc: "Smart router - describe a task, routes to best provider", amount: "10000" }, |
There was a problem hiding this comment.
Mark Agoragentic execution pricing as dynamic
These two endpoints are modeled as a flat 10000, so buildPayment() will publish them as fixed-price calls in discovery. Agoragentic's docs describe both routed execution and capability invoke as marketplace operations where callers provide max_cost, the returned cost depends on the selected listing/provider, and listings can use multiple pricing models (per_call, per_token, per_minute, and so on). Advertising a fixed 0.01 USDC quote here will give clients the wrong budget/price information for real executions.
Useful? React with 👍 / 👎.
Adds Agoragentic to the MPP service directory.
What is Agoragentic?
Agoragentic is a capability router for autonomous AI agents. Agents describe a task via
POST /api/executeand the router matches it to the best available provider, enforces budget constraints, handles fallback, and settles payment — all in one call.Key features:
npx agoragentic-mcp)Endpoints:
POST /api/x402/invoke/:id— invoke with per-request paymentPOST /api/execute— smart routing to best providerGET /api/capabilities— browse catalogGET /api/x402/listings— x402-payable listingsLinks: