io.github.freshfos/dropcoin-invoice

German e-invoicing: generate XRechnung 3.0, pre-check and extract (incl. ZUGFeRD PDF). Paid.

Paid verification

No sponsored paid call yet.

Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.

Quality grade

How grading works

C+ 58.0 / 100

Availability 40.0 / 40

Endpoint responded (HTTP 200)

Payability 18.0 / 20

✓ Answers a real HTTP 402 challenge
✓ Publishes a /.well-known/x402 descriptor
✓ Payment address on record
✗ Settlement network declared
✓ Price declared

Demand 0.0 / 40

Payment address on record, not yet queried on-chain

Owner verified 0.0 / 3

Nobody has claimed this listing yet

Endpoint last checked 5 h ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 80/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 58.0/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements	9/10	Findings: missing: settlement network declared. missing: settlement network declared
Live 402 challenge	20/25	Endpoint reachable; its 402 challenge was seen earlier (338 ms).
x402 version	n/a	x402 version not observed yet.
Signed descriptor	n/a	No x402 standard defines a signed descriptor.
Uptime (30 days)	15/15	32/32 probes succeeded over 30 days (100%).
Resource declaration	10/10	Declares 3 paid resource(s).
Verified identity	5/10	Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags	1/5	not seen in a source for over 30 days; declares x402.
Security declaration	n/a	Payment is the access control for an x402 resource.

Applicable criteria total 75 points, scaled to 100.

Responsiveness: Responsive (338 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest. Qualifies the payment claim; adds no points.

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 10,060 reachable x402 APIs in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 55% of peers; This listing 80 · peer median 78
Latency: Faster than 32% of peers; This listing 338 ms · peer median 205 ms

Where it loses the most points, and how to win them back

Live 402 challenge −5 — Answer the paid path with a valid 402 challenge.
Now: Endpoint reachable; its 402 challenge was seen earlier (338 ms).
Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags −4 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days; declares x402.

How many agent tools actually work · All statistics

Paid endpoints

3 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

POST https://invoice-api.dropcoin.workers.dev/v1/invoice/xrechnung

Generate a German XRechnung 3.0 e-invoice (UBL 2.1 XML, EN 16931) from plain JSON. Totals, VAT breakdown and rounding are computed server-side per the official rules — the most common source of rejected e-invoices. Returns the XML plus computed totals and warnings.

POST https://invoice-api.dropcoin.workers.dev/v1/invoice/validate

Pre-check an incoming e-invoice (XRechnung UBL or CII XML) against the priority EN 16931 / XRechnung business rules: mandatory fields, Leitweg-ID, payment data, and cent-exact recalculation of all sums and VAT. Findings carry official rule IDs (BR-CO-10 etc.). A pre-check, not the official KoSIT val

POST https://invoice-api.dropcoin.workers.dev/v1/invoice/extract

Extract structured JSON (parties, lines, totals, payment data) from an e-invoice: XRechnung UBL/CII XML or a ZUGFeRD/Factur-X PDF (the embedded XML is pulled from the PDF). Ideal for agents ingesting incoming invoices.

How to call

cURL · x402-fetch / x402-axios will auto-handle 402

curl -sS -i -X GET https://invoice-api.dropcoin.workers.dev/mcp  # expect HTTP 402 Payment Required (about 0.03 USDC/call)

MCP endpoint

https://invoice-api.dropcoin.workers.dev/mcp

/.well-known/x402.json

https://invoice-api.dropcoin.workers.dev/.well-known/x402

Listed in

Directories this entry was found in.

mcp since 2026-08-08