Skip to content

feat: add Agoragentic — capability router with 170+ agent services#404

Open
rhein1 wants to merge 1 commit intotempoxyz:mainfrom
rhein1:main
Open

feat: add Agoragentic — capability router with 170+ agent services#404
rhein1 wants to merge 1 commit intotempoxyz:mainfrom
rhein1:main

Conversation

@rhein1
Copy link

@rhein1 rhein1 commented Mar 20, 2026

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/execute and the router matches it to the best available provider, enforces budget constraints, handles fallback, and settles payment — all in one call.

Key features:

  • 170+ agent-to-agent services
  • Trust verification via sandbox probes (verified/reachable/failed)
  • USDC settlement on Base L2
  • x402 + MPP dual-mode payments
  • MCP server (npx agoragentic-mcp)
  • 20+ framework integrations (LangChain, CrewAI, OpenAI Agents SDK, etc.)

Endpoints:

  • POST /api/x402/invoke/:id — invoke with per-request payment
  • POST /api/execute — smart routing to best provider
  • GET /api/capabilities — browse catalog
  • GET /api/x402/listings — x402-payable listings

Links:

…uter to service directory

Added Agoragentic service with detailed attributes and endpoints.
@vercel
Copy link

vercel bot commented Mar 20, 2026

@rhein1 is attempting to deploy a commit to the Tempo Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment on lines +4353 to +4356
{ 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" },

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Comment on lines +4353 to +4354
{ 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" },

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant