x402 Agent Tollbooth

ai_intel

Read-only

Deep AI Vulnerability & Intelligence Engine. Scans contracts and code for logic vulnerabilities and exploits on Base. Cost: 0.001 USDC on Base & Solana (100% gasless).

Input Schema

Name	Required	Description
`prompt`	No	Analysis prompt or contract source code to audit
`limited_review`	No	Explicitly purchase only a limited source-pattern review at the quoted endpoint price; this mode does not provide an AI audit or patch
`contractAddress`	No	Base smart contract address to audit

Output Schema

Name	Required	Description	Default
`limits`	No
`method`	No
`status`	Yes
`service`	Yes
`endpoint`	Yes
`findings`	No
`safety_proven`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / limited_review

Added value: +{
+  "default": false,
+  "description": "Explicitly purchase only a limited source-pattern review at the quoted endpoint price; this mode does not provide an AI audit or patch",
+  "type": "boolean"
+}

Changed8 schema fields changedOct 27, 2026
- addedOutput schema / properties / findings
```
Added value: +{
+  "type": "array"
+}
```
- removedOutput schema / properties / intel
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / latency_ms
```
Removed value: -{
-  "type": "integer"
-}
```
- addedOutput schema / properties / limits
```
Added value: +{
+  "type": "array"
+}
```
- addedOutput schema / properties / method
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / safety_proven
```
Added value: +{
+  "type": "boolean"
+}
```
- removedOutput schema / properties / score
```
Removed value: -{
-  "type": "integer"
-}
```
- removedOutput schema / properties / verified_by
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "endpoint": {
+      "type": "string"
+    },
+    "intel": {
+      "type": "string"
+    },
+    "latency_ms": {
+      "type": "integer"
+    },
+    "score": {
+      "type": "integer"
+    },
+    "service": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "verified_by": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "service",
+    "endpoint"
+  ],
+  "type": "object"
+}

First observedOct 16, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations lack – a 0.001 USDC charge on Base and Solana, gasless – but it never says how payment is triggered or settled, which is the key operational unknown for a paid call.

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

Conciseness4/5

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

Three short sentences, front-loaded with the capability before the cost. 'Deep AI Vulnerability & Intelligence Engine' is marketing padding that does not earn its place, but the remainder is tight.

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?

With an output schema, annotations, and zero required params, the definition covers purpose and price adequately. It is still incomplete on the two things an agent most needs for a paid, sibling-overlapping tool: how payment is executed and why to pick this over contract_audit.

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

Parameters3/5

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

Schema coverage is 100% and all three parameters are documented in-schema, including the limited_review caveat. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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?

States a specific verb and resource: scans contracts and code for logic vulnerabilities and exploits on Base. The domain (Base contracts) is pinned down, but it never distinguishes itself from the sibling contract_audit, which reads as the same job.

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?

Usage is only implied – an agent can infer 'call this to audit a contract on Base' – but there is no explicit when-to-use, no when-not-to-use, and no routing to arbitrage_scan, contract_audit, or smart_router. The cost note informs a decision but does not guide tool selection.

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

All x402 Agent Tollbooth 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.