usdc_x402_payments_intel
Real-time analytics on x402 protocol USDC micropayments for MCP endpoints on Base network. Unique competitive advantage: aggregates internal production telemetry (our own traffic data) with on-chain USDC Transfer events and Bazaar marketplace listings — data no external competitor can access. Fou...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/usdc-x402-payments-intel.md
What usdc_x402_payments_intel does on Gapup Mcp
AI agents use usdc_x402_payments_intel to commit financial operations through Gapup Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | Yes | Analytics mode: facilitator_stats=network-wide settlements | endpoint_intel=per-URL analytics | agent_caller_profile=per-wallet analytics | price_radar=price di |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
category | string | — | Tool category for price_radar mode. Defaults to all. |
period_days | number | — | Lookback window in days (5-90, default 30) |
endpoint_url | string | — | MCP endpoint URL for endpoint_intel mode (e.g. https://mcp.gapup.io/mcp) |
wallet_address | string | — | EVM wallet address for agent_caller_profile mode (0x...) |
Parameters from the server's own tool schema.
Why usdc_x402_payments_intel is rated Critical
This tool directly interfaces with USDC payment flows on the Base network, processes on-chain financial transactions, and provides analytics over live payment settlement data. The x402 per-call billing model and integration with Coinbase CDP API for payment facilitation place this squarely in the Financial category.
From the tool's definition Real-time analytics on x402 protocol USDC micropayments... aggregates internal production telemetry with on-chain USDC Transfer events... facilitator_stats — Coinbase x402 facilitator settlement statistics (volume, count, top payees/payers)... x402 per-call
Attacks that exploit this kind of access
The rule that runs usdc_x402_payments_intel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For usdc_x402_payments_intel, this is the rule to start with:
Any call to usdc_x402_payments_intel is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every usdc_x402_payments_intel call is checked against it from then on.
Questions about usdc_x402_payments_intel
Real-time analytics on x402 protocol USDC micropayments for MCP endpoints on Base network. Unique competitive advantage: aggregates internal production telemetry (our own traffic data) with on-chain USDC Transfer events and Bazaar marketplace listings — data no external competitor can access. Four modes: (1) facilitator_stats — Coinbase x402 facilitator settlement statistics (volume, count, top payees/payers). Uses Coinbase CDP API if COINBASE_X402_API_KEY is set; falls back to Base mainnet RPC scan of USDC transfers to known facilitator addresses. (2) endpoint_intel — Per-MCP-endpoint analytics: tx count, USDC volume, unique callers, success rate, catalog size. For gapup-mcp.io endpoints: reads internal JSONL telemetry (richest data source, unique). (3) agent_caller_profile — Anonymous profile of a calling agent wallet: tx count, USDC spent, top endpoints, inferred persona (depth-seeker / bulk-scanner / generalist / researcher / explorer). Wallet anonymised via SHA-256. (4) price_radar — USDC price distribution by tool category (data_lookup / synthesis / compliance / competitive) from Bazaar + internal catalog. Returns median, P25, P75. Network: Base mainnet. USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Cache: 30 min LRU. Timeout per source: 8s. Optional env: COINBASE_X402_API_KEY (higher-fidelity facilitator stats). It is categorised as a Financial tool in the Gapup Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
usdc_x402_payments_intel accepts 6 parameters: mode, async, category, period_days, endpoint_url, wallet_address. Required: mode. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for usdc_x402_payments_intel: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Gapup Mcp. Nothing to install.
usdc_x402_payments_intel is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the usdc_x402_payments_intel rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for usdc_x402_payments_intel. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
usdc_x402_payments_intel is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
Across the catalogue