passabsent from every registry#6 by calls of 5 on this host
1.25 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-08 06:01 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-08 07:30 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 1.25 USDC
- Networks
- 2
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 107 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
At api.govparse.io, device clearances search takes GET requests, is listed in neither registry at the last pull, and falls under search by TOLL's rules.
device clearances search is priced at 1.25 USDC on Base.
Its declared inputs are the query parameters company, pathway and product_code.
device clearances search accepts payment on Base and Solana, 2 options in all, to 2 different wallets.
A response from device clearances search, as declared, includes rows and total_matched.
device clearances search answered the sweep of 2026-10-08 with a valid 402, as at every sweep since 2026-09-11.
device clearances search shares api.govparse.io with 4 other listed endpoints and is 6th by calls.
device clearances search takes 1% of the calls counted across api.govparse.io.
In the trailing 30 days: one call, one payer.
device clearances search was last called 55 days before the snapshot.
Closest in price to device clearances search within search: search at blockrun.ai and serp read at api.kadec0.xyz.
device clearances search is near the top of prices in search; 100% of comparable listings are cheaper.
The wallet paid by device clearances search is the payee of 64 endpoints on one host.
device clearances search was missing from the Coinbase registry at the pull of 2026-10-08, confirmed at the pull of 2026-10-08; that is registry presence, not liveness.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-10-08 06:01 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 1.25 USDC | exact | 0x3873d1…567129 |
| Coinbase | solana: | USDC | 1.25 USDC | exact | BdcZbENF…J3LmaB |
the checks, as of 2026-10-08 11:40 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-08 11:40 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 11:01 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 11:42 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 10:23 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 13:19 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 06:53 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 16:03 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 08:50 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 08:15 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 20:24 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 17:33 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-23 07:24 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 07:37 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 07:59 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 05:59 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 14:40 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 05:51 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 05:50 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 06:07 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:38 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:32 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:49 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 11:41 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-08 07:30 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"company": "Medtronic",
"pathway": "510k",
"product_code": "DXY"
}
},
"output": {
"type": "json",
"example": {
"rows": [
{
"state": "CA",
"pathway": "510k",
"applicant": "Pacesetter Systems",
"entity_id": null,
"decision_id": "K850651",
"device_name": "PROGRAMALITH III-3 MODEL 231 PULSE GENERATOR",
"generic_name": null,
"product_code": "DXY",
"date_received": "1985-02-19",
"decision_code": "SESE",
"decision_date": "1985-04-01",
"clearance_type": "Traditional",
"advisory_committee": "Cardiovascular",
"decision_description": "Substantially Equivalent"
}
],
"total_matched": 1
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "device clearances search on api.govparse.io". https://tollindex.com/e/api-govparse-io-v1-fda-device-clearances-search-a6e755. Accessed [access date].
BibTeX
@misc{toll-e-api-govparse-io-v1-fda-device-clearances-search-a6e755-2026-11-01,
author = {TOLL},
title = {device clearances search on api.govparse.io},
howpublished = {\url{https://tollindex.com/e/api-govparse-io-v1-fda-device-clearances-search-a6e755}},
year = {2026},
month = {11},
note = {Frozen at its last observation, 2026-11-01 21:59 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.