boundary-guard-x402.onrender.com

Deploy and scale any app or agent from your first user to your billionth. Build faster on intuitive cloud infrastructure for the modern web.

SearchLiveeip155:8453Exactvia cdp
Activity
Nothing indexed for this service or its provider yet. Not a claim that it is unused — only that we hold no record.
$8.43
Verified settled volume
823 settlements proven x402 by their on-chain EIP-3009 marker.
$0.010
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-06-08 04:30Z
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x4200ab5Af9E541b6A89eb39EeF3140f83D9De8b0

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.01USDC≈ $0.01 USD
on Base · exact scheme

Pay 0.01 USDC on Base to 0x4200…De8b0. The signed payment is good for 5 minutes.

USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
10000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0x4200ab5Af9E541b6A89eb39EeF3140f83D9De8b0",
    "amount": "10000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "name": "Boundary Guard",
  "tags": [
    "agents",
    "crm",
    "lead-gen",
    "extraction",
    "contact-extraction",
    "sales-intelligence",
    "prospecting"
  ],
  "bazaar": {
    "info": {
      "input": {
        "body": {
          "text": "sales@example.com, 555-123-4567, https://example.com/demo"
        },
        "type": "http",
        "method": "POST",
        "bodyType": "json"
      },
      "output": {
        "type": "json",
        "example": {
          "urls": [
            "https://example.com/demo"
          ],
          "counts": {
            "urls": 1,
            "emails": 1,
            "phones": 1,
            "domains": 1
          },
          "emails": [
            "sales@example.com"
          ],
          "phones": [
            "555-123-4567"
          ],
          "domains": [
            "example.com"
          ]
        }
      }
    },
    "name": "Boundary Guard",
    "tags": [
      "agents",
      "crm",
      "lead-gen",
      "extraction",
      "contact-extraction",
      "sales-intelligence",
      "prospecting"
    ],
    "method": "POST",
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method",
            "bodyType",
            "body"
          ],
          "properties": {
            "body": {
              "type": "object",
              "required": [
                "text"
              ],
              "properties": {
                "text": {
                  "type": "string"
                }
              }
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "POST"
              ],
              "type": "string"
            },
            "bodyType": {
              "enum": [
                "json"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object",
              "required": [
                "emails",
                "phones",
                "urls",
                "domains",
                "counts"
              ],
              "properties": {
                "urls": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                },
                "counts": {
                  "type": "object",
                  "additionalProperties": {
                    "type": "integer"
                  }
                },
                "emails": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                },
                "phones": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                },
                "domains": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                }
              }
            }
          }
        }
      }
    },
    "docsUrl": "https://boundary-guard-x402.onrender.com/docs",
    "service": {
      "id": "boundary-guard",
      "name": "Boundary Guard",
      "docsUrl": "https://boundary-guard-x402.onrender.com/docs",
      "llmsUrl": "https://boundary-guard-x402.onrender.com/llms.txt",
      "category": "Data",
      "provider": "Boundary Guard",
      "categories": [
        "Data",
        "Infra",
        "Search",
        "Security",
        "Agent observability",
        "Lead enrichment"
      ],
      "openapiUrl": "https://boundary-guard-x402.onrender.com/openapi.json",
      "homepageUrl": "https://boundary-guard.vercel.app",
      "providerUrl": "https://boundary-guard.vercel.app",
      "providerName": "Boundary Guard",
      "provider_url": "https://boundary-guard.vercel.app",
      "categoryAliases": [
        "Data",
        "Infra",
        "Search",
        "Security",
        "Agent observability",
        "Lead enrichment"
      ],
      "agenticMarketUrl": "https://agentic.market/?service=boundary-guard-x402-onrender-com",
      "x402WellKnownUrl": "https://boundary-guard-x402.onrender.com/.well-known/x402",
      "agenticMarketServiceId": "boundary-guard-x402-onrender-com"
    },
    "category": "Data",
    "keywords": [
      "agents",
      "crm",
      "lead-gen",
      "extraction",
      "contact-extraction",
      "sales-intelligence",
      "prospecting"
    ],
    "provider": "Boundary Guard",
    "categories": [
      "Data",
      "Infra",
      "Search",
      "Security",
      "Agent observability",
      "Lead enrichment"
    ],
    "openapiUrl": "https://boundary-guard-x402.onrender.com/openapi.json",
    "homepageUrl": "https://boundary-guard.vercel.app",
    "providerUrl": "https://boundary-guard.vercel.app",
    "serviceName": "Boundary Guard",
    "buyerQueries": [
      "contact extraction",
      "lead intake cleanup",
      "crm prep",
      "prospecting",
      "sales intelligence"
    ],
    "discoverable": true,
    "providerName": "Boundary Guard",
    "provider_url": "https://boundary-guard.vercel.app",
    "targetBuyers": [
      "sales and lead-enrichment agents",
      "research agents",
      "MCP tool routers"
    ],
    "categoryAliases": [
      "Data",
      "Infra",
      "Search",
      "Security",
      "Agent observability",
      "Lead enrichment"
    ],
    "x402WellKnownUrl": "https://boundary-guard-x402.onrender.com/.well-known/x402",
    "marketplaceSearchTitle": "Boundary Guard - Contact Extract API for Lead Intake Cleanup",
    "currentHighValueEndpoint": "/lead-brief-lite",
    "marketplaceSearchDescription": "x402 contact extraction API for lead intake cleanup, CRM prep, and source-bound contact parsing. Extract emails, phones, URLs, and domains from messy public text before enrichment or outreach.",
    "currentHighValueEndpointCategory": "Data"
  },
  "agentic": {
    "name": "Boundary Guard",
    "tags": [
      "agents",
      "crm",
      "lead-gen",
      "extraction",
      "contact-extraction",
      "sales-intelligence",
      "prospecting"
    ],
    "docsUrl": "https://boundary-guard-x402.onrender.com/docs",
    "service": "Boundary Guard",
    "category": "Data",
    "keywords": [
      "agents",
      "crm",
      "lead-gen",
      "extraction",
      "contact-extraction",
      "sales-intelligence",
      "prospecting"
    ],
    "provider": "Boundary Guard",
    "categories": [
      "Data",
      "Infra",
      "Search",
      "Security",
      "Agent observability",
      "Lead enrichment"
    ],
    "openapiUrl": "https://boundary-guard-x402.onrender.com/openapi.json",
    "homepageUrl": "https://boundary-guard.vercel.app",
    "providerUrl": "https://boundary-guard.vercel.app",
    "serviceName": "Boundary Guard",
    "discoverable": true,
    "providerName": "Boundary Guard",
    "provider_url": "https://boundary-guard.vercel.app",
    "categoryAliases": [
      "Data",
      "Infra",
      "Search",
      "Security",
      "Agent observability",
      "Lead enrichment"
    ],
    "agenticMarketUrl": "https://agentic.market/?service=boundary-guard-x402-onrender-com",
    "x402WellKnownUrl": "https://boundary-guard-x402.onrender.com/.well-known/x402",
    "agenticMarketServiceId": "boundary-guard-x402-onrender-com",
    "marketplaceSearchTitle": "Boundary Guard - Contact Extract API for Lead Intake Cleanup",
    "marketplaceSearchDescription": "x402 contact extraction API for lead intake cleanup, CRM prep, and source-bound contact parsing. Extract emails, phones, URLs, and domains from messy public text before enrichment or outreach."
  },
  "docsUrl": "https://boundary-guard-x402.onrender.com/docs",
  "service": "Boundary Guard",
  "category": "Data",
  "keywords": [
    "agents",
    "crm",
    "lead-gen",
    "extraction",
    "contact-extraction",
    "sales-intelligence",
    "prospecting"
  ],
  "provider": "Boundary Guard",
  "categories": [
    "Data",
    "Infra",
    "Search",
    "Security",
    "Agent observability",
    "Lead enrichment"
  ],
  "openapiUrl": "https://boundary-guard-x402.onrender.com/openapi.json",
  "homepageUrl": "https://boundary-guard.vercel.app",
  "marketplace": {
    "name": "Boundary Guard",
    "tags": [
      "agents",
      "crm",
      "lead-gen",
      "extraction",
      "contact-extraction",
      "sales-intelligence",
      "prospecting"
    ],
    "docsUrl": "https://boundary-guard-x402.onrender.com/docs",
    "service": "Boundary Guard",
    "category": "Data",
    "keywords": [
      "agents",
      "crm",
      "lead-gen",
      "extraction",
      "contact-extraction",
      "sales-intelligence",
      "prospecting"
    ],
    "provider": "Boundary Guard",
    "categories": [
      "Data",
      "Infra",
      "Search",
      "Security",
      "Agent observability",
      "Lead enrichment"
    ],
    "openapiUrl": "https://boundary-guard-x402.onrender.com/openapi.json",
    "homepageUrl": "https://boundary-guard.vercel.app",
    "providerUrl": "https://boundary-guard.vercel.app",
    "serviceName": "Boundary Guard",
    "discoverable": true,
    "providerName": "Boundary Guard",
    "provider_url": "https://boundary-guard.vercel.app",
    "categoryAliases": [
      "Data",
      "Infra",
      "Search",
      "Security",
      "Agent observability",
      "Lead enrichment"
    ],
    "agenticMarketUrl": "https://agentic.market/?service=boundary-guard-x402-onrender-com",
    "x402WellKnownUrl": "https://boundary-guard-x402.onrender.com/.well-known/x402",
    "agenticMarketServiceId": "boundary-guard-x402-onrender-com",
    "marketplaceSearchTitle": "Boundary Guard - Contact Extract API for Lead Intake Cleanup",
    "marketplaceSearchDescription": "x402 contact extraction API for lead intake cleanup, CRM prep, and source-bound contact parsing. Extract emails, phones, URLs, and domains from messy public text before enrichment or outreach."
  },
  "providerUrl": "https://boundary-guard.vercel.app",
  "serviceName": "Boundary Guard",
  "discoverable": true,
  "providerName": "Boundary Guard",
  "provider_url": "https://boundary-guard.vercel.app",
  "categoryAliases": [
    "Data",
    "Infra",
    "Search",
    "Security",
    "Agent observability",
    "Lead enrichment"
  ],
  "agenticMarketUrl": "https://agentic.market/?service=boundary-guard-x402-onrender-com",
  "x402WellKnownUrl": "https://boundary-guard-x402.onrender.com/.well-known/x402",
  "agenticMarketServiceId": "boundary-guard-x402-onrender-com",
  "marketplaceSearchTitle": "Boundary Guard - Contact Extract API for Lead Intake Cleanup",
  "marketplaceSearchDescription": "x402 contact extraction API for lead intake cleanup, CRM prep, and source-bound contact parsing. Extract emails, phones, URLs, and domains from messy public text before enrichment or outreach."
}

Provenance

Seen in the source catalog
2026-06-08 04:30Z
Last indexed by Roundhouse
2026-07-08 03:00Z
Last enriched (probe, favicon, geo)
2026-09-21 16:45Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 404
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

Nothing indexed for this service or its provider yet. Not a claim that it is unused — only that we hold no record. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service boundary-guard-x402.onrender.com and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=boundary-guard-x402.onrender.com'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://boundary-guard-x402.onrender.com/contact-extract, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.