Roundhouse AI

eu-verify

Pay-per-call APIs and MCP tools for AI agents: French company registry, EU VAT validation, insolvency records, IBAN/LEI checks, EU tenders. USDC on Base via x402 - no API key.

DataLiveeip155:8453Exactvia cdp
https://x402-datashop-production.up.railway.app/v1/fr/communes
FranceCommunesInseeGeoReference
Settlements · 30d
450↑ 156%
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days.
$10.65
Verified settled volume
1,190 settlements proven x402 by their on-chain EIP-3009 marker.
$0.0010
Listed price
As published in the catalog. Always read the live 402 before paying.
—
Calls · 30d
Upstream's own call count for this endpoint, not ours.
—
Unique payers · 30d
Never called
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x6ab8efe305cce67daa48c97bde29c04402822dff

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.001USDC≈ $0.001 USD
on Base · exact scheme

Pay 0.001 USDC on Base to 0x6ab8…22dff. The signed payment is good for 5 minutes.

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

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "type": "http",
        "method": "GET",
        "queryParams": {
          "cp": "31700"
        }
      },
      "output": {
        "type": "json",
        "example": {
          "count": 2,
          "source": "geo.api.gouv.fr decoupage administratif (Etalab, INSEE/IGN data, Licence Ouverte 2.0)",
          "communes": [
            {
              "epci": {
                "nom": "Toulouse Métropole",
                "code": "243100518"
              },
              "name": "Beauzelle",
              "region": {
                "nom": "Occitanie",
                "code": "76"
              },
              "insee_code": "31056",
              "population": 8713,
              "departement": {
                "nom": "Haute-Garonne",
                "code": "31"
              },
              "postal_codes": [
                "31700"
              ]
            },
            {
              "epci": {
                "nom": "Toulouse Métropole",
                "code": "243100518"
              },
              "name": "Blagnac",
              "region": {
                "nom": "Occitanie",
                "code": "76"
              },
              "insee_code": "31069",
              "population": 27604,
              "departement": {
                "nom": "Haute-Garonne",
                "code": "31"
              },
              "postal_codes": [
                "31700"
              ]
            }
          ]
        }
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method"
          ],
          "properties": {
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "GET",
                "HEAD",
                "DELETE"
              ],
              "type": "string"
            },
            "queryParams": {
              "type": "object",
              "properties": {
                "cp": {
                  "type": "string",
                  "description": "5-digit postal code, e.g. 31700"
                },
                "lat": {
                  "type": "number",
                  "description": "Latitude (with lon: commune containing the point)"
                },
                "lon": {
                  "type": "number",
                  "description": "Longitude (with lat)"
                },
                "nom": {
                  "type": "string",
                  "description": "Commune name, fuzzy search"
                },
                "code": {
                  "type": "string",
                  "description": "5-character INSEE commune code, e.g. 31056"
                }
              }
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-07-15 21:19Z
Last indexed by Roundhouse
2026-07-15 23:40Z
Last enriched (probe, favicon, geo)
2026-09-22 04:45Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 402
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

No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. 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 eu-verify 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=eu-verify'
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://x402-datashop-production.up.railway.app/v1/fr/communes, 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.