Sellat x402 · Proof of Existence & Qualified Timestamping
payment-ready until 2026-11-03
Agent-only pay-per-request proof of existence with Polygon and Bitcoin anchoring ($0.01 USDC), and qualified eIDAS timestamping ($0.90 USDC) via x402 on Base.
Payout address in review
The live 402 response asks to be paid at a different address than this listing shows. The change has not been reviewed yet, so this page and the API keep the previous address until it is. Check the address in the 402 response you receive before you pay.
- Listed address
0xEC7c3Bbf17352aF760f2D89B0170477DaC5ae25D- Live 402 address
0xeDeb27856FfB8c313931B2DCE0f8375F27f4d87asince 2026-10-27 11:32:09 UTC, last seen 2026-10-27 13:41:05 UTC- Network
- Base, USDC
- Endpoint
POST /proofs
Call it x402 v2
x402 v2
- Base URL
- https://sellat.app/api/v2
- Payment
- x402 v2, header channel
$ curl -i -X POST 'https://sellat.app/api/v2/proofs' An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.
Endpoints 1 paid route on sellat.app
Prices as captured in the 402 response: $0.01, unchanged since first capture.
Example 402 response
Endpoints and prices
| Method | Path | Description | Price | Network | Asset | 402 channel | Captured |
|---|---|---|---|---|---|---|---|
| POST | / | Timestamp and notarize any file or data by its SHA-256 hash: blockchain proof of existence and document integrity, anchored on Polygon in minutes and attested on Bitcoin (OpenTimestamps); blockchain notarization, not a notary act. Returns proof_id, certificate, proof.json and evidence ZIP, verifiable without Sellat. Use when you must prove that exact data existed by now and is intact. | $0.01 | Base | USDC | header | since 10-27 |
Payment evidence
402 payload captured at . Check evidence JSON · Measurement methodology.
1 payload captured by the monitor.
152 lines, scroll inside
{
"error": "PAYMENT-SIGNATURE header is required Paying this offer accepts Sellat's terms and conditions, https://sellat.app/en/condiciones (version 2026-10-26); the version is recorded with the payment.",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xeDeb27856FfB8c313931B2DCE0f8375F27f4d87a",
"amount": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"resource": {
"url": "https://sellat.app/api/v2/proofs",
"tags": [
"timestamp",
"notarize",
"proof-of-existence",
"eidas",
"qualified-timestamp"
],
"iconUrl": "https://sellat.app/sellat-favicon.png",
"mimeType": "application/json",
"description": "Timestamp and notarize any file or data by its SHA-256 hash: blockchain proof of existence and document integrity, anchored on Polygon in minutes and attested on Bitcoin (OpenTimestamps); blockchain notarization, not a notary act. Returns proof_id, certificate, proof.json and evidence ZIP, verifiable without Sellat. Use when you must prove that exact data existed by now and is intact.",
"serviceName": "Sellat"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"hash": "3d015831c0288a69c80ff28998d540781423735ce937e2390c153b938c781322",
"name": "sellat-example-20261027113209-728842fa.txt",
"metadata": {
"ref": "optional"
}
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"id": "<proof_id>",
"hash": "<sha256>",
"next": "POST /api/v2/proofs/{id}/qualified adds the eIDAS qualified timestamp (RFC 3161) for 0.90 USD",
"urls": {
"self": "https://sellat.app/api/v2/proofs/<id>",
"proof_json": "https://sellat.app/api/v2/proof/<id>.json",
"certificate": "https://sellat.app/certificate/<id>",
"evidence_zip": "https://sellat.app/api/v2/proofs/<id>/evidence.zip"
},
"state": "queued → anchored (minutes)",
"api_key": "<shown once: read-only key for this wallet’s proofs>",
"created": true,
"payment": {
"charged": true,
"amount_usd": "0.01",
"transaction": "<tx hash on Base>"
},
"proof_id": "<proof_id: use it in POST /api/v2/proofs/{id}/qualified>",
"anchoring": {
"policy": "fast"
}
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object"
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"headers": {
"type": "object",
"additionalProperties": {
"type": "string"
}
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
},
"pathParams": {
"type": "object",
"additionalProperties": {
"type": "string"
}
},
"queryParams": {
"type": "object",
"additionalProperties": {
"type": "string"
}
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
},
"x402Version": 2
} Can I trust it score from our own monitoring
score from our own monitoring
#54 of 169 in Verification. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.
- Reliability
- 100% uptime since 10-27
- Compliance
- A 14/14 checks pass
- Price
- $0.01 p48 in Verification
- Risk
- clean no risk flag
- Traction
- $0.00 30d 0 buyers
14/14 compliance checks
- 402 payload captured
- accepts[] array present
- payTo address recoverable
- payTo at accepts[0].payTo (conformant shape)
- payTo is a valid on-chain address
- atomic price declared
- atomic price in a sane range
- asset (token) address declared
- network resolves to CAIP-2
- payment scheme declared
- served over HTTPS
- declares the current x402 version (2)
- EIP-712 domain parameters present on every EVM entry
- x402 v2 envelope delivered in the payment-required header
402 terms unchanged since 2026-10-27. Last up 2026-10-27.
── Site signals
- homepage reachable
- openapi doc
- pricing page
- llms.txt
- robots.txt
- terms page
How the score works
What the score read on this service: status online, 100% uptime, latest daily rollup (no 30d window yet), 325ms response p95, x402 compliance 14 of 14, $0.01 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.
The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.
Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.
It is a score inside Verification, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 169 listings, this one among them: the same 169 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.
Traction is a conservative undercount.
All measured facts
What it does
Agent-only pay-per-request proof of existence with Polygon and Bitcoin anchoring ($0.01 USDC), and qualified eIDAS timestamping ($0.90 USDC) via x402 on Base. No signup or API key required.
Sellat x402 · Proof of Existence & Qualified Timestamping is a listed x402 Verification API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.
Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.
Page rendered at . This response time is separate from the observation and computation times attached to each measurement.
Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.
Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.
Observed daily coverage: 2026-09-28 to 2026-10-27 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.
Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.
x402 List home · Services · Verification
- uptime · latest daily rollup
- -
- uptime 7d
- -
- uptime 30d
- -
- uptime 90d
- -
- response p95
- 325ms
- avg response
- 325ms
- total checks
- 1
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
- price (min)
- $0.01
- category percentile (min)
- p48 in Verification
- endpoints / prices
- 1 / 1
- model
- flat
- stability
- 100%
No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.
- domain age
- -
- registrar
- -
- hosting
- custom
- domain created
- ---
Identity facts, not a risk score.
- assessment volume 30d
- $0.00
- exact assessment volume 30d (USD)
- 0
- assessment recorded at (UTC)
- 2026-10-27T11:33:40.053Z
- buyers 30d
- 0
- settlements 30d
- 0
- measured since
- --- (start of our harvest window)
- last settlement
- ---
- top buyer share
- -
- top 3 buyers share
- -
- concentrated volume
- no
- trend 7d vs 30d
- -
- networks
- eip155:8453
- volume all-time
- $0
- settlements all-time
- 0
- median settlement 30d
- -
- max settlement 30d
- -
Assessment volume uses the latest 30d assessment. Over time sums daily address snapshots, rounded to cents and refreshed separately. The two sources can differ in timing, precision and shared-address attribution. Amounts use cents for comparison; known sub-cent values keep up to 12 significant digits. The exact stored assessment value is shown above.
Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.
Top buyer share lowers the on-chain traction part of the ranking score behind this page's verdict and /best, by up to half when one address holds all 30d volume. The Recommended and Highest volume sorts of the services list do not use it; they use the Concentrated volume rule instead.
- member since
- 2026-10-27
Recent checks
| Checked at (UTC) | Status | HTTP | Response | Endpoints |
|---|---|---|---|---|
| Online | 402 | 1330ms | 1 | |
| Online | 402 | 905ms | 1 | |
| Online | 402 | 693ms | 1 | |
| Online | 402 | 412ms | 1 | |
| Online | 402 | 562ms | 1 | |
| Online | 402 | 343ms | 1 | |
| Online | 402 | 1210ms | 1 | |
| Online | 402 | 626ms | 1 | |
| Online | 402 | 325ms | 1 |
Changes0 in 30d
No changes recorded in the last 30 days.
Over time
- Volume 30d
- $0.00
- Uptime
- no completed-day data
More charts
09-28 to 10-27* UTC
Each series spans only the dates it has data for. Every series is also served as JSON at /api, /scores, /volume and /buyers.
Values
* today so far, partial (UTC).
The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.
Daily snapshot total, 30d: $3.25, peak $1.83 on 10-19. The visible 30d total in Traction comes from the latest assessment. These sources can differ in their window, refresh time, cent rounding and shared-address attribution.
Daily address snapshots: 2026-09-28 to 2026-10-27 UTC; * today so far, partial (UTC). Daily snapshots store cents. A recorded $0.00 with settlements cannot distinguish exact zero from volume rounded away. Lost precision is unavailable here.
Settlement volume uses the stored USD valuation of tracked payments; it is distinct from token quantities. USD-pegged assets are valued at 1 USD per token in these rollups. The measured settlement floor does not cover all payments to this service.
Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.
| Day | Volume | Buyers | Settlements | Uptime | Response | Compliance | Price percentile | Site signals |
|---|---|---|---|---|---|---|---|---|
| 2026-10-18 | $1.42 | 1 | 4 | no data | no data | no data | no data | no data |
| 2026-10-19 | $1.83 | 1 | 5 | no data | no data | no data | no data | no data |
| 2026-10-20 | no data | no data | no data | no data | no data | no data | no data | no data |
| 2026-10-21 | no data | no data | no data | no data | no data | no data | no data | no data |
| 2026-10-22 | no data | no data | no data | no data | no data | no data | no data | no data |
| 2026-10-23 | no data | no data | no data | no data | no data | no data | no data | no data |
| 2026-10-24 | no data | no data | no data | no data | no data | no data | no data | no data |
| 2026-10-25 | no data | no data | no data | no data | no data | no data | no data | no data |
| 2026-10-26 | no data | no data | no data | no data | no data | no data | no data | no data |
| 2026-10-27* | no data | no data | no data | 100% | 579.67ms | 14/14 | p48 | 4/6 |
Alternatives in Verification
5 of 168 other ranked services in Verification, ordered by the same measured score.
Own this service?
Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.
Update this listingEarn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.
Verify this service ($0.25)Embed a badge
HTML
<a href="https://x402-list.com/services/ sellat-x402-proof-of-existence-qualified-timestamping? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ sellat-x402-proof-of-existence-qualified-timestamping.svg" alt="Sellat x402 — Proof of Existence & Qualified Timestamping listed on x402-list" height="28"> </a>
Markdown
[](https://x402-list.com/ services/ sellat-x402-proof-of-existence-qualified-timestamping? utm_source=badge& utm_medium=referral& utm_campaign=embed)
HTML, live uptime variant
<a href="https://x402-list.com/services/ sellat-x402-proof-of-existence-qualified-timestamping? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ sellat-x402-proof-of-existence-qualified-timestamping.svg? data=uptime" alt="Sellat x402 — Proof of Existence & Qualified Timestamping uptime on x402-list" height="28"> </a>
Delisting
To request delisting, email info@x402-list.com with the service name, slug, or URL. Removal is free and does not require proof of ownership. Contact.