TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
32,435

sql ddl compatibility derived

api.zfinia.comOtherderived

POST https://api.zfinia.com/x402/v1/sql-ddl-compatibility

passabsent from every registry#7 by calls of 15 on this host

0.28 USDC

per call, as the listing declares it on eip155:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-09 13:14 UTC · method

Validation state
pass
as of 2026-10-09 05:54 UTC · method · sweep daily-2026-10-09
Uptime, 7 / 30 / 90 days
— / 83% / 83%
as of 2026-10-09 05:54 UTC · method · 0 of 0 in 7d, 5 of 6 in 30d, 5 of 6 in 90d
Calls, trailing 30 days
1
as of 2026-10-09 13:14 UTC · method
Unique payers, trailing 30 days
1
as of 2026-10-09 13:14 UTC · method
Last called
2026-10-05 02:07 UTC
as of 2026-10-09 13:14 UTC · method
First observed by TOLLderived
2026-10-05
as of 2026-10-05 05:36 UTC · method · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.28 USDC
as of 2026-10-09 13:14 UTC · method · on eip155:8453
Networks
1
as of 2026-10-09 13:14 UTC · method

Counters

12 observations, 1 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 3,825 endpoints in Other that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 1: 2,938 in the category are counted higher and 886 lower.

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.

In words

Of api.zfinia.com's 15 listings, sql ddl compatibility ranks tied 7th by calls with 9 others.

Callers of sql ddl compatibility supply a json body with the fields role, after and before.

A response from sql ddl compatibility, as declared, includes role, limits, passed, complete, findings, compatible and 2 others.

sql ddl compatibility drew a single call from a single payer in the trailing 30 days.

The last call to sql ddl compatibility came 9 days before the snapshot, 2026-10-05.

A call to sql ddl compatibility costs 0.28 USDC on Base, as declared.

Of the calls counted across api.zfinia.com, sql ddl compatibility takes 4%.

TOLL files sql ddl compatibility under the "other" category: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.

sql ddl compatibility answered the sweep of 2026-10-09 with a valid 402, passing 5 of 6 sweeps since 2026-10-05.

Closest in price to sql ddl compatibility within the "other" category: research newsfeed at win.oneshotagent.com and page speed test at api.strale.io.

sql ddl compatibility is near the top of prices in the "other" category; 98% of comparable listings are cheaper.

The wallet paid by sql ddl compatibility is the payee of 179 endpoints across 5 hosts.

The seller's tags on sql ddl compatibility are sql, database migration, schema compatibility and release gate.

sql ddl compatibility 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.

Payment options as declared

the payment options, as of 2026-10-09 13:14 UTC · method

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.28 USDCexact0x25e824…6a9608

Preflight checks at the last sweep

the checks, as of 2026-10-09 05:54 UTC · methodendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-09 05:54 UTCpass0daily-2026-10-09
2026-10-08 07:38 UTCpass0daily-2026-10-08
2026-10-07 06:50 UTCpass0daily-2026-10-07
2026-10-06 07:39 UTCpass0daily-2026-10-06
2026-10-05 07:07 UTCpass0daily-2026-10-05
2026-10-05 05:42 UTCfail1new-after-daily-2026-10-05

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. absence from Coinbase confirmed, rule v1
  2. absent from Coinbase at this pull
  3. listed in Coinbase

Declared input and output, as listed

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": {
      "role": "both",
      "after": "CREATE TABLE customers (\n  id        bigint       NOT NULL PRIMARY KEY,\n  email     varchar(255) NOT NULL UNIQUE,\n  region    varchar(2)\n);\n\nCREATE TABLE orders (\n  id           bigint        NOT NULL PRIMARY KEY,\n  customer_id  bigint        NOT NULL REFERENCES customers(id),\n  total        numeric(12,2) NOT NULL,\n  status       varchar(20)   NOT NULL,\n  currency     char(3)       NOT NULL,\n  placed_at    timestamp with time zone NOT NULL,\n  CONSTRAINT orders_customer_status_uq UNIQUE (customer_id, status)\n);",
      "before": "CREATE TABLE customers (\n  id        integer      NOT NULL PRIMARY KEY,\n  email     varchar(255) NOT NULL UNIQUE,\n  region    varchar(2)\n);\n\nCREATE TABLE orders (\n  id           integer       NOT NULL PRIMARY KEY,\n  customer_id  integer       NOT NULL REFERENCES customers(id),\n  total        numeric(12,2) NOT NULL DEFAULT 0,\n  status       varchar(20),\n  internal_ref text,\n  placed_at    timestamp with time zone NOT NULL\n);"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "role": "both",
      "limits": {
        "maxTables": 400,
        "maxDdlBytes": 262144,
        "maxFindings": 500,
        "maxStatements": 2000,
        "maxColumnsPerTable": 500
      },
      "passed": false,
      "complete": true,
      "findings": [
        {
          "code": "COLUMN_TYPE_WIDENED",
          "table": "customers",
          "breaks": [
            "readers"
          ],
          "column": "id",
          "detail": "customers.id widens from integer to bigint. The database accepts this, but a client that decoded the old type can overflow on a value the new one permits."
        },
        {
          "code": "COLUMN_TYPE_WIDENED",
          "table": "orders",
          "breaks": [
            "readers"
          ],
          "column": "id",
          "detail": "orders.id widens from integer to bigint. The database accepts this, but a client that decoded the old type can overflow on a value the new one permits."
        },
        {
          "code": "COLUMN_TYPE_WIDENED",
          "table": "orders",
          "breaks": [
            "readers"
          ],
          "column": "customer_id",
          "detail": "orders.customer_id widens from integer to bigint. The database accepts this, but a client that decoded the old type can overflow on a value the new one permits."
        }
      ],
      "compatible": false,
      "request_id": "example-request",
      "service_id": "sql_ddl_compatibility",
      "assumptions": [
        "A PRIMARY KEY column is treated as NOT NULL whether or not it says so, because the server enforces that.",
        "Widening inside one type family is reported for readers and not for writers: the database accepts the wider value, and the client that decoded the narrower type is the thing that overflows.",
        "A change crossing type families is reported as breaking for both, since neither the stored values nor the client binding carries across."
      ],
      "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...",
        "A renamed column is reported as one removed and one added, because a declaration cannot distinguish a rename from an unrelated pair without the migration that performed it. sql_migration_blast_radius ..."
      ],
      "observed_at": "2026-10-02T00:00:00.000Z",
      "not_examined": [],
      "tables_added": [],
      "tables_after": 2,
      "finding_count": 8,
      "tables_before": 2,
      "breaking_count": 8,
      "service_version": "1.0.0",
      "tables_compared": 2,
      "columns_compared": 8,
      "findings_by_code": {
        "COLUMN_REMOVED": 1,
        "COLUMN_TYPE_WIDENED": 3,
        "REQUIRED_COLUMN_ADDED": 1,
        "COLUMN_BECAME_NOT_NULL": 1,
        "COLUMN_DEFAULT_REMOVED": 1,
        "UNIQUE_CONSTRAINT_ADDED": 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, "sql ddl compatibility on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-sql-ddl-compatibility-3b8330. Accessed [access date].

BibTeX

@misc{toll-e-api-zfinia-com-x402-v1-sql-ddl-compatibility-3b8330-2026-10-13,
  author = {TOLL},
  title = {sql ddl compatibility on api.zfinia.com},
  howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-sql-ddl-compatibility-3b8330}},
  year = {2026},
  month = {10},
  note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about sql ddl compatibility, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint 3b8330ff19a8ada715c011062f4a376ddd688c7e2d7b94806d04723bd9b96faf from wallet 0x25e8245f07d5e4873987293dad666afbe56a9608

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.