View daily earnings, market cap, volume and coverage →
api.zfinia.com · api.zfinia.com · Security
| Day · UTC | Earned | Gross volume | Refunds | Observed transfers | Market cap | Revenue coverage |
|---|---|---|---|---|---|---|
| 2026-10-26 | — | — | — | — | — | none |
| 2026-10-25 | — | — | — | — | — | none |
| 2026-10-24 | — | — | — | — | — | none |
| 2026-10-23 | — | — | — | — | — | none |
| 2026-10-22 | — | — | — | — | — | none |
| 2026-10-21 | — | — | — | — | — | none |
| 2026-10-20 | — | — | — | — | — | none |
View daily history → · UTC days; today's figures are partial.
Audit a real request against the OpenAPI document it should satisfy. Matches the operation the way a router would, checks every path, query and header parameter against its declared schema, validates the body against the declared media type, and reports whether the credential the declared security scheme expects is present. You supply the request, so this works against an API nothing external can reach.
Quoted from x402 Bazaar · source record · read 2026-10-26
No settled payment on record. Earnings for this service are unknown — not zero. The source counts 1 calls in 30 days, which at the published price is roughly $0.14 of activity. Activity is not revenue; no charge has been reconciled for it.
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.
{
"body": {
"request": {
"headers": {
"X-Api-Key": "redacted"
},
"method": "GET",
"path": "/orders",
"query": {
"page": "first"
}
},
"specification": {
"components": {
"schemas": {
"Order": {
"properties": {
"id": {
"type": "string"
},
"status": {
"enum": [
"open",
"shipped",
"disputed"
],
"type": "string"
},
"tenant_id": {
"type": "string"
},
"total": {
"type": "number"
}
},
"required": [
"id",
"total",
"tenant_id"
],
"type": "object"
}
},
"securitySchemes": {
"apiKey": {
"in": "query",
"name": "api_key",
"type": "apiKey"
}
}
},
"info": {
"title": "Orders API",
"version": "2.0.0"
},
"openapi": "3.1.0",
"paths": {
"/orders": {
"get": {
"operationId": "listOrdersV2",
"parameters": [
{
"in": "query",
"name": "tenant",
"required": true,
"schema": {
"type": "string"
}
}
],
"responses": {
"200": {
"content": {
"application/json": {
"schema": {
"items": {
"$ref": "#/components/schemas/Order"
},
"type": "array"
}
}
},
"description": "A page of orders"
}
},
"summary": "List orders"
},
"parameters": [
{
"in": "query",
"name": "page",
"schema": {
"minimum": 1,
"type": "integer"
}
}
],
"post": {
"operationId": "createOrder",
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/Order"
}
}
},
"required": true
},
"responses": {
"201": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/Order"
}
}
},
"description": "Created"
}
},
"summary": "Create an order"
}
},
"/orders/{id}": {
"get": {
"deprecated": true,
"operationId": "getOrder",
"parameters": [
{
"in": "path",
"name": "id",
"schema": {
"type": "string"
}
}
],
"responses": {
"200": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/Order"
}
}
},
"description": "The order"
},
"404": {
"description": "Not found"
}
},
"summary": "Fetch one order"
}
}
},
"security": [
{
"apiKey": []
}
]
}
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": {
"assumptions": [
"A literal path segment is preferred over a template, as a router would, so /pets/mine is audited against its own operation rather than /pets/{id}.",
"Path, query and header values arrive as text, so a value declared as an integer is checked against its text form rather than rejected for being a string.",
"Header names are compared case-insensitively."
],
"checked": {
"body": false,
"header_parameters": 0,
"path_parameters": 0,
"query_parameters": 2
},
"complete": true,
"conformant": false,
"finding_count": 3,
"findings": [
{
"code": "TYPE_MISMATCH",
"detail": "GET /orders: query parameter page Expected integer, found string.",
"location": "query",
"operation": "GET /orders",
"parameter": "page"
},
{
"code": "REQUIRED_PARAMETER_MISSING",
"detail": "GET /orders: required query parameter tenant is absent from the request.",
"location": "query",
"operation": "GET /orders",
"parameter": "tenant"
},
{
"code": "SECURITY_REQUIREMENT_UNMET",
"detail": "GET /orders requires apiKey and the request carries no matching credential.",
"operation": "GET /orders"
}
],
"findings_by_code": {
"REQUIRED_PARAMETER_MISSING": 1,
"SECURITY_REQUIREMENT_UNMET": 1,
"TYPE_MISMATCH": 1
},
"limitations": [
"Conformance of one request against the supplied specification. Whether the specification is correct is not assessed.",
"conformant is true only when every declared constraint for the matched operation was evaluated and none failed."
],
"limits": {
"maxClientOperations": 200,
"maxFindings": 500,
"maxOperations": 500,
"maxRequestBodyBytes": 262144
},
"matched_operation": "GET /orders",
"matched_path_template": "/orders",
"not_examined": [],
"observed_at": "2026-10-02T00:00:00.000Z",
"operation_deprecated": false,
"operation_id": "listOrdersV2",
"path_variables": [],
"request_id": "example-request",
"service_id": "openapi_parameter_contract_audit",
"service_version": "1.0.0"
},
"type": "json"
}
Examples are the provider's own, not a call we made.
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://api.zfinia.com/x402/v1/openapi-parameter-contract-audit
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-26 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-26 |
| Payment | Provider claim |
1 rail: Base · payee 0x25e8245f07d5e4873987293dad666afbe56a9608
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-10-26 |
| Pricing | Provider claim |
0.14 USDC per call
EvidenceAtomic amount 140000 = 0.14 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-10-26 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-26 |
| Provider | Provider claim |
api.zfinia.com
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-26 |
| Usage | Verified |
1 calls / 1 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-26. Letzter Aufruf laut Quelle: 2026-10-04T07:53:01.867Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-26 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.
Email deliverability & domain security check — validates SPF, DKIM (multi-selector), and DMARC, detects spoofing and misconfigurations, and returns an A–F email security grade with transparent deductions. Anti-spam / ant...
Full website audit in one call: accessibility (WCAG 2.1 A/AA via axe-core), on-page SEO, HTTP security headers and page speed / page weight, from a single browser load of one URL. Cheaper than four separate calls; if any...
CVE vulnerability lookup. Returns security vulnerability records by CVE id or keyword from the NIST National Vulnerability Database and GitHub Security Advisories, each with CVSS score, severity, CWE weakness class, affe...
Resolve DNS records using DNS-over-HTTPS and return structured JSON for infrastructure, security, and agent workflows.
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.