DropEngine x402 Agent Services

check_wallet

Paid Wallet Risk Check ($0.02 USDC on Base). Call before an agent sends funds to, accepts value from, grants an approval to, or interacts with an unfamiliar address. Checks whether the address is a wallet or contract and reads basic on-chain metadata. Sanctions, scam, drainer, mixer, and malicious-address intelligence are unknown unless a trusted provider is configured; without one, the result is cautious and low-confidence, not a safety certification. Never send private keys or seed phrases.

Agent entry points: risky external action → use Agent Action Gate when a combined action-specific safety assessment is needed; unclear capability/provider → use free /api/discover; constrained comparison between callable alternatives → use paid route_tool; known single capability → call the direct tool; multi-step objective → read the matching workflow recipe and call only relevant steps. Workflows are stateless recipes, not executors; calls are paid separately and are not bundle charged. Agent Action Gate does not approve payment, sign or broadcast transactions, evaluate seller reputation, replace transaction simulation, replace route_tool, or replace human approval.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	Yes
`address`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`next`	No
`chain`	Yes
`error`	No
`cached`	Yes
`result`	No
`status`	No
`address`	Yes
`onchain`	Yes
`payment`	No
`sources`	Yes
`success`	Yes
`agent_ux`	No
`contract`	Yes
`degraded`	Yes
`warnings`	Yes
`exposures`	Yes
`scam_risk`	Yes
`checked_at`	Yes
`reputation`	Yes
`risk_level`	Yes
`risk_score`	Yes
`address_type`	Yes
`drainer_risk`	Yes
`mixer_exposure`	Yes
`recommendation`	Yes
`known_malicious`	Yes
`risk_confidence`	Yes
`sanctions_match`	Yes
`suspicious_activity`	Yes
`data_freshness_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 8, 2026

addedOutput schema / properties / agent_ux

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "meta": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "next": {
+      "items": {},
+      "type": "array"
+    },
+    "payment": {
+      "additionalProperties": false,
+      "properties": {
+        "execution_status": {
+          "enum": [
+            "not_started",
+            "succeeded",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "not_required",
+            "required",
+            "settled",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "execution_status"
+      ],
+      "type": "object"
+    },
+    "result": {},
+    "status": {
+      "enum": [
+        "succeeded",
+        "failed",
+        "partial",
+        "outcome_unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "result",
+    "error",
+    "meta",
+    "payment",
+    "next"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / error

Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / meta

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / next

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedOutput schema / properties / payment

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "execution_status": {
+      "enum": [
+        "not_started",
+        "succeeded",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "not_required",
+        "required",
+        "settled",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "execution_status"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result
```
Added value: +{}
```

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "succeeded",
+    "failed",
+    "partial",
+    "outcome_unknown"
+  ],
+  "type": "string"
+}

First observedSep 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and discloses key behaviors: the $0.02 USDC cost on Base, the limited confidence without a configured trusted provider, and the explicit warning that it is not a safety certification. It also warns never to send private keys or seed phrases, which is critical operational guidance.

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?

The description is front-loaded with purpose, price, and primary usage, then follows with routing guidance. It is slightly long because the 'Agent entry points' paragraph is generic boilerplate, but most sentences still earn their place by clarifying alternatives or constraints.

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

Completeness4/5

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

The description covers purpose, usage context, cost, limitations, and safety warnings, and the output schema handles return values. The main gap is the lack of explicit parameter semantics for 'chain' and 'address', though the simple schema and regex pattern mitigate this for a two-parameter tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the two parameters. It mentions 'address' but provides no format details beyond what the regex already enforces, and it only loosely implies a chain by saying 'on Base' without explaining the allowed base-sepolia option or the chain parameter's role.

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

Purpose5/5

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

The description names a specific tool: a paid wallet risk check that determines whether an address is a wallet or contract and reads basic on-chain metadata. It also explicitly distinguishes this tool from siblings like Agent Action Gate, route_tool, and /api/discover, so an agent can identify its role without opening other schemas.

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

Usage Guidelines5/5

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

It states exactly when to call it: before sending funds to, accepting value from, granting approval to, or interacting with an unfamiliar address. The 'Agent entry points' section then maps broader needs to alternatives such as Agent Action Gate for combined risk assessments, route_tool for comparisons, and workflow recipes for multi-step objectives.

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

All DropEngine x402 Agent Services 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?