# x402_discover

Search for x402 paid API endpoints that can answer a question or provide data. Discovery powered by Decixa (5,500+ verified x402 endpoints) with local registry fallback. Searches across the entire x402 ecosystem — not just Alderpost endpoints. Local registry includes premium endpoints backed by VirusTotal, People Data Labs, Hunter.io, AbuseIPDB, Qualys SSL Labs, NIH RxNorm, US Census Bureau, OpenWeather, The Odds API. Categories: security, company/business, threat intelligence, sales/leads, compliance, health/drug, property/location, sports, and any x402 capability indexed by Decixa. Examples: - query

Agent View of the PolicyLayer registry record for `x402_discover`. HTML page: https://policylayer.com/tools/8randonpickart5-x402-buyer-mcp/x402-discover

## Facts

- Tool: `x402_discover`
- Server: X402 Buyer (`8randonpickart5/x402-buyer-mcp`) — https://policylayer.com/tools/8randonpickart5-x402-buyer-mcp.md
- Homepage: https://github.com/8randonpickart5/x402-buyer-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

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

## Why x402_discover is rated Low

This tool retrieves information about available paid APIs without creating, modifying, or deleting data, and without executing arbitrary code. It is purely a discovery/search mechanism. While the broader system involves financial transactions (via AgentCash payments mentioned in server description), this specific tool only reads data about available endpoints.

From the tool's own definition: "Tool performs search and discovery functionality across API endpoints: 'Search for x402 paid API endpoints' and 'Searches across the entire x402 ecosystem.' The description emphasizes querying and indexing ('Decixa index', 'local registry') with no mention of…"

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call x402_discover to retrieve information from X402 Buyer without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches X402 Buyer:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "x402_discover": {}
  }
}
```

## Other tools on X402 Buyer (3)

- `x402_research` — Execute — https://policylayer.com/tools/8randonpickart5-x402-buyer-mcp/x402-research.md
- `x402_call` — Financial — https://policylayer.com/tools/8randonpickart5-x402-buyer-mcp/x402-call.md
- `x402_balance` — Read — https://policylayer.com/tools/8randonpickart5-x402-buyer-mcp/x402-balance.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=8randonpickart5-x402-buyer-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/8randonpickart5-x402-buyer-mcp
