x402 merchant
geoprimitives$0.005 / callapi.geoprimitives.dev
MarineDepthNauticalNoaa-encAlaska

Give it a latitude and longitude and it answers with what the nautical chart says about the water there: the depth range of the charted depth area containing the position, the nearest charted sounding and how far away it is, and the chart's own zone of confidence for that area. Parameters go in the query string: this is a GET, there is no body. NOT FOR NAVIGATION, stated first because it is a condition of using the source. This is derived from NOAA Electronic Navigational Charts and redistributed; it is not an official NOAA ENC and does not meet federal chart carriage regulations under 33 CFR 164 or SOLAS chapter V, which only charts from NOAA or a certified NOAA ENC distributor do. Every response repeats this under `disclaimer`. NOAA and NOAA ENC are registered trademarks of NOAA, which does not endorse this service. COVERAGE is 65 NOAA ENC cells of usage bands 3, 4 and 5 over five working areas of southeast and southcentral Alaska: Sitka Sound; Kasaan Bay and Clarence Strait; Metlakatla, Ketchikan and Revillagigedo Channel; Juneau, Gastineau Channel and Lynn Canal; and Cordova with eastern Prince William Sound. It is not statewide, it is not the whole coast, and the small-scale cells that would make it look wider were deliberately left out. The coverage check reads the coordinate, so it runs in the handler after payment rather than in front of the 402: a position off the charts is quoted like any other and then refused with outside_coverage. A refusal does not settle and nothing is charged, but it costs a signature and a round trip, so check the coverage first. Every response repeats it under `coverage`. NOTHING IS INTERPOLATED, and that is the difference between this and GET /v1/elevation. Terrain is a continuous surface and sampling it between pixels is legitimate; a chart is a set of assertions a hydrographer made, and averaging two of them invents a depth nobody surveyed. So `depthAreaMinimum` is DRVAL1 of the charted depth area the position falls inside, the shoalest depth that area is guaranteed to hold, and `nearestSounding` is a real charted sounding with the geodesic distance to it. The two routinely disagree and are meant to: a sounding is a measurement at a point and the area is a guarantee over a region. The guarantee is the number to navigate a plan by; the sounding tells you how the area was arrived at. WHICH CHART ANSWERS: ENC cells overlap on purpose, so a position in Sitka sits on a 1:12,000 harbour cell, a 1:45,000 approach cell and a 1:180,000 coastal cell at once, and they do not agree because the smaller scales generalise. The largest-scale cell covering the position wins outright, usage band first and then compilation scale, which is the rule an ECDIS follows. The response names the cell, its band, its scale, its edition and its NOAA issue date, and lists any cell it consulted first that charted no depth area there. SURVEY QUALITY is on every answer as the chart's CATZOC zone of confidence, with the position and depth accuracy that zone implies, and the survey start and end dates when the chart gives them. Read it before you trust a depth. NOAA's own warning applies to all of it: much of the depth information on NOAA charts is from surveys conducted before 1940 and the shoreline is more than 20 years old. Zone A1 is a modern full-coverage survey; zone D or U means the chart is telling you it does not know. DATUMS: depths are metres below Mean Lower Low Water, which is the US chart datum, so a real depth at a real moment is this number plus the tide. Heights on the same charts are above Mean High Water. Positions are WGS 84. Reproject with POST /v1/transform if you are in State Plane or NAD27; the datum shift matters here, since a NAD27 Alaskan position is over a hundred metres from its WGS 84 one. VINTAGE: the charts are a snapshot taken on 2026-05-02. NOAA reissues ENCs weekly for Notice to Mariners and this store does not follow them, so a cell here can be behind NOAA's current edition. The cell edition, update number and issue date that answered are in `source` for exactly that comparison. REFUSALS that cost nothing: a position with no charted depth area is `no_depth_area`, which means land, a drying area the chart gives no depth for, or a gap between cells, and it is refused rather than answered with null. A position off the charts is `outside_coverage`. A chart object that cannot be read is a 503, not a guess. For what is in the way rather than how deep it is, use GET /v1/marine/hazards, which returns charted rocks, obstructions and wrecks within a radius.

MerchantReport

0x76a5…8fce

0x76a51b5dd3729950b3b60c17f19252d221968fceExplorer
Received
$4.40↑ 121%
Last 7d vs prior 7d
Paid out
$0.00
Last 7d vs prior 7d
Settlements
885↑ 121%
Last 7d vs prior 7d
11
Distinct counterparties
Over the whole indexed history

Received $4.40 of the $258.60M Roundhouse has indexed across 713,391 walletsless than 0.0001% of it.

Chains (from the recent scan): Base (885)

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartySent to themReceived from themSettlementsLast
0xf82d…55f6$0.00$4.098185h agoGraph
0xe60a…2428$0.00$0.233333d agoGraph
0x8d2a…7d37$0.00$0.022417d agoGraph
0xc533…2d7a$0.00$0.02324d agoGraph
0x5760…7db6$0.00$0.00513d agoGraph
0x7dd8…17d2$0.00$0.00517d agoGraph
0xe3ba…3fb3$0.00$0.00519d agoGraph
0xf331…194c$0.00$0.005113d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

93% of observed volume is with a single counterparty, in all 885 observed settlements.

Organic volume $4.40 of $4.40 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase5h ago0x0d8460…1e9593
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase12h ago0x59b757…cf7dc0
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase18h ago0x0adc6a…47be80
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase20h ago0x3cfe1f…5240fe
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase23h ago0xf10d2a…13f592
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0x1892cb…cee6e7
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0x33e7d4…3adafb
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0x0c5cf0…9e9312
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0xa7b60a…a701b6
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0xcd076e…32edfe
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0x5ab944…88b2e2
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0xfd39c2…1e044e
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0xbbf483…dce286
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0x1ac7f6…cfbac8
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0xc215ee…b64979
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0x64e147…a383a6
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0xe4daba…83493d
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase1d ago0x13d826…5f5f7a
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase2d ago0x29fb9d…92e2a7
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase2d ago0x382b79…791d99
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase2d ago0xe19b34…9d778b
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase2d ago0x46b46c…1aef00
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase2d ago0xf2f7ba…af2685
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase3d ago0x0f07a1…a580c9
0xf82d…55f60x76a5…8fceBase$0.005100%coinbase3d ago0x3063d1…ad89e4

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check 0x76a5…8fce's payment record before paying it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/merchants/0x76a51b5dd3729950b3b60c17f19252d221968fce

Open skill.md
Show the prompt
Using Roundhouse, tell me whether this x402 merchant is worth paying: how many distinct
agents have paid it, how recently, and for what.

  Merchant wallet: 0x76a51b5dd3729950b3b60c17f19252d221968fce

curl -s 'https://api.roundhouseai.io/v0/merchants/0x76a51b5dd3729950b3b60c17f19252d221968fce'
curl -s 'https://api.roundhouseai.io/v0/entities/0x76a51b5dd3729950b3b60c17f19252d221968fce/settlements?limit=50'

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.