skim402.com

Skim turns any URL into clean, agent-ready markdown — or typed JSON via /v1/extract. Pure x402: agents pay $0.002 per read ($0.015 per structured extract) in USDC on Base. No signup, no API keys.

OtherLiveeip155:8453Exactvia cdp
Calls · 30d
11↑ 12%
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 22 snapshots so far.
$15.38
Verified settled volume
3,461 settlements proven x402 by their on-chain EIP-3009 marker.
$0.0050
Listed price
As published in the catalog. Always read the live 402 before paying.
10
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-09-23 06:42Z
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x63AE98f3363B346a94Fcc1CBcB621F1C2B1Fcddc

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

Pay 0.005 USDC on Base to 0x63AE…Fcddc. The signed payment is good for 2 minutes.

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

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "type": "http",
        "method": "GET",
        "queryParams": {
          "limit": 50
        }
      },
      "output": {
        "type": "json",
        "example": {
          "asOf": "2026-08-02T12:00:00Z",
          "feed": "entity-formations",
          "count": 1,
          "crawl": {
            "status": "ok",
            "durationMs": 2400,
            "lastCrawlAt": "2026-08-02T12:00:00Z"
          },
          "items": [
            {
              "at": "2026-08-02T12:00:00Z",
              "id": 1601,
              "url": "https://data.ny.gov/resource/n9v6-gdp6.json?dos_id=7981000",
              "kind": "entity-formation",
              "title": "BLUE HARVEST PRODUCTIONS LLC — new NY DOMESTIC LIMITED LIABILITY COMPANY",
              "source": "ny-dos",
              "payload": {
                "country": "US",
                "official": true,
                "sourceUrl": "https://data.ny.gov/resource/n9v6-gdp6.json?dos_id=7981000",
                "entityName": "BLUE HARVEST PRODUCTIONS LLC",
                "entityType": "DOMESTIC LIMITED LIABILITY COMPANY",
                "filingDate": "2026-07-30",
                "publishedAt": "2026-07-30T00:00:00.000Z",
                "entityNumber": "7981000",
                "jurisdiction": "NY",
                "registeredAgent": "Sloane & Partners LLP"
              },
              "summary": "BLUE HARVEST PRODUCTIONS LLC filed in NY on 2026-07-30; registered agent: Sloane & Partners LLP. Official registry record."
            }
          ],
          "ttlSeconds": 21600,
          "degradedSources": []
        }
      }
    },
    "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"
              ],
              "type": "string"
            },
            "queryParams": {
              "type": "object",
              "required": [],
              "properties": {
                "limit": {
                  "type": "integer",
                  "maximum": 100,
                  "minimum": 1,
                  "description": "Maximum number of formation items to return (default 50, no upper cap). Newest-first by filing date. Without a jurisdictions filter, results are balanced: each jurisdiction is guaranteed a floor of newest rows (up to 25) so high-volume registries can't crowd the others out; use limit=100 for the fullest balanced window."
                },
                "jurisdictions": {
                  "type": "string",
                  "description": "Optional comma-separated jurisdiction codes to include (NY, TX, NM, UK, CA). Example: jurisdictions=NY,CA. Omit for a balanced mix of all covered jurisdictions."
                }
              }
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-09-23 06:42Z
Last indexed by Roundhouse
2026-09-24 13:40Z
Last enriched (probe, favicon, geo)
2026-09-13 19:15Z
x402 version
2
Max timeout
120s
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

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 22 snapshots so far. 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 skim402.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=skim402.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://skim402.com/api/v2/signal/entity-formations/latest, 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.