Genexxis paid agent tools (x402)

intel_credit

Prepaid credit for all Genexxis x402 APIs: pay 1 USDC once, get 1.50 USD of credit (+50%) valid 90 days, spent at list price on any of our ~90 routes priced up to $0.01 (SEC EDGAR, sanctions, CVE, DeFi, odds, web read...). Send it as Authorization: Bearer gxc_... : no per-call signature or gas. Failed calls are refunded. Price: $1.00 USDC per call, paid with x402 on Base.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "intel_credit"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does add real behavior: 90-day validity, failed calls refunded, no per-call signature or gas, and payment via x402 on Base. It stops short of stating whether invoking the tool itself triggers an on-chain purchase, whether credit is bound to a wallet, or what is returned, which are the critical behavioral facts for a payment tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The value proposition is front-loaded and useful, but the text is dense and mixes purchase terms, spend mechanics, and route samples. It also repeats pricing inconsistently ('pay 1 USDC once' versus 'Price: $1.00 USDC per call'), which muddies rather than clarifies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter purchase tool with no output schema, the description should say what the caller receives (presumably the gxc_ token) and what happens on invocation. It covers pricing, validity and refunds but omits the return artifact and the invocation side effect, leaving a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so per the baseline the schema is trivially complete and the description need not explain inputs. Nothing in the description misrepresents the parameter surface.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the resource (prepaid credit for the Genexxis x402 APIs) and its economics clearly, so an agent can tell it is the credit-purchase tool rather than a data route. However, it never states a direct verb ('purchase/obtain credit') and does not differentiate itself from siblings such as safepay_pass, leaving the agent to infer the exact action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains what the credit covers (~90 routes up to $0.01, with examples) and how to spend it via 'Authorization: Bearer gxc_...', but it never says 'call this tool to buy credit' nor when to prefer this over per-call x402 payment or the safepay variants. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Genexxis paid agent tools (x402) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?