passabsent from every registry#7 by calls of 15 on this host
0.3 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-09 13:14 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 67% / 67%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-05 02:07 UTC
- First observed by TOLLderived
- 2026-10-05
- Pricederived
- 0.3 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 12 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.
Of api.zfinia.com's 15 listings, sql migration blast radius ranks tied 7th by calls with 9 others.
The request to sql migration blast radius is a json body with the field migration.
A response from sql migration blast radius, as declared, includes limits, passed, complete, findings, low_risk, request_id and 2 others.
sql migration blast radius drew a single call from a single payer in the trailing 30 days.
The last call to sql migration blast radius came 9 days before the snapshot, 2026-10-05.
A call to sql migration blast radius costs 0.3 USDC on Base, as declared.
Of the calls counted across api.zfinia.com, sql migration blast radius takes 4%.
TOLL files sql migration blast radius under the "other" category: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.
sql migration blast radius answered the sweep of 2026-10-09 with a valid 402, passing 4 of 6 sweeps since 2026-10-05.
Closest in price to sql migration blast radius within the "other" category: research newsfeed at win.oneshotagent.com and page speed test at api.strale.io.
sql migration blast radius is near the top of prices in the "other" category; 98% of comparable listings are cheaper.
The wallet paid by sql migration blast radius is the payee of 179 endpoints across 5 hosts.
The seller's tags on sql migration blast radius are sql, database migration, deployment risk and release gate.
sql migration blast radius was missing from the Coinbase registry at the pull of 2026-10-09, confirmed at the pull of 2026-10-10; 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-09 13:14 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.3 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-09 06:35 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-09 06:35 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 08:03 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 07:18 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 08:07 UTC | fail | 1 | daily-2026-10-06 |
| 2026-10-05 07:29 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-05 05:43 UTC | fail | 1 | new-after-daily-2026-10-05 |
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-10-05 02:07 UTC · method
The input and output block
{
"input": {
"body": {
"migration": "ALTER TABLE orders ALTER COLUMN id TYPE bigint;\nALTER TABLE orders ALTER COLUMN customer_id TYPE bigint;\nALTER TABLE orders ALTER COLUMN status SET NOT NULL;\nALTER TABLE orders ADD COLUMN currency char(3) NOT NULL;\nALTER TABLE orders DROP COLUMN internal_ref;\nALTER TABLE orders RENAME COLUMN placed_at TO created_at;\nCREATE INDEX orders_status_idx ON orders (status);"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxTables": 400,
"maxDdlBytes": 262144,
"maxFindings": 500,
"maxStatements": 2000,
"maxColumnsPerTable": 500
},
"passed": false,
"complete": true,
"findings": [
{
"code": "TABLE_REWRITE",
"table": "orders",
"detail": "alter_column_type on orders.id rewrites the table. Changing a column type rewrites the table and every index on it, blocking readers and writers for the duration.",
"blocking": "full-rewrite",
"operation": "alter_column_type"
},
{
"code": "TABLE_REWRITE",
"table": "orders",
"detail": "alter_column_type on orders.customer_id rewrites the table. Changing a column type rewrites the table and every index on it, blocking readers and writers for the duration.",
"blocking": "full-rewrite",
"operation": "alter_column_type"
},
{
"code": "FULL_TABLE_SCAN_LOCK",
"table": "orders",
"detail": "set_not_null on orders.status scans every row while holding a lock. Setting NOT NULL scans every row to verify it, holding a lock that blocks writers for the scan.",
"blocking": "full-scan",
"operation": "set_not_null"
}
],
"low_risk": false,
"request_id": "example-request",
"service_id": "sql_migration_blast_radius",
"assumptions": [
"Lock behaviour is stated for current PostgreSQL and MySQL 8 defaults. An older server rewrites the table for operations listed here as brief, so a stated profile is a floor rather than a promise.",
"Adding a nullable column with no default is treated as a catalogue change, because both engines have done it that way for several major versions.",
"An index build is counted as blocking unless concurrent_index_builds says otherwise, since the non-concurrent form is the default spelling."
],
"limitations": [
"Only the declared schema is read. No database is contacted and no rows are seen, so nothing here reports whether a migration will succeed against the data actually present.",
"DDL is read as a documented subset: CREATE TABLE, ALTER TABLE, CREATE and DROP INDEX, DROP TABLE, TRUNCATE, GRANT and REVOKE. Anything else — a view, function, trigger or data statement — is listed in...",
"Statement order is read as given. Whether the migration runs in one transaction, and therefore whether a later failure rolls back an earlier statement, is not declared in the DDL and is not inferred."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"finding_count": 7,
"tables_touched": [
"orders"
],
"columns_touched": [
"orders.currency",
"orders.customer_id",
"orders.id"
],
"operations_read": 7,
"service_version": "1.0.0",
"statement_count": 7,
"findings_by_code": {
"TABLE_REWRITE": 2,
"FULL_TABLE_SCAN_LOCK": 2,
"DESTRUCTIVE_AND_IRREVERSIBLE": 1,
"RENAME_BREAKS_IN_FLIGHT_CLIENTS": 1,
"REQUIRED_COLUMN_ADDED_WITHOUT_DEFAULT": 1
},
"destructive_count": 1,
"irreversible_count": 1,
"operations_by_kind": {
"add_column": 1,
"drop_column": 1,
"create_index": 1,
"set_not_null": 1,
"rename_column": 1,
"alter_column_type": 2
},
"table_rewrite_count": 2
}
}
}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, "sql migration blast radius on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-sql-migration-blast-radius-4745f3. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-sql-migration-blast-radius-4745f3-2026-10-13,
author = {TOLL},
title = {sql migration blast radius on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-sql-migration-blast-radius-4745f3}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.