api.invoket.com
Generates a PDF version of an invoice from your input data.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"error": "PAYMENT-SIGNATURE header is required. Free trial on request: send the header `X-402-Trial: 1` on this call and on the signed retry to have a free-trial option added to accepts[].",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x4465825B0ac713aA2Fa07Ea29023020804A128ee",
"amount": "100000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
],
"resource": {
"url": "https://api.invoket.com/invoice/generate-pdf",
"tags": [
"compliance",
"verification",
"fraud-prevention",
"regulatory-data",
"weather"
],
"iconUrl": "https://invoket.com/apple-touch-icon.png",
"mimeType": "application/json",
"description": "Before your agent bills a customer: get the whole Factur-X file it sends and the customer reads - a PDF/A-3B embedding the EN 16931 CII XML, the hybrid invoice mandated by the French 2026-2027 reform. Post simple business JSON (parties, lines, VAT), get a file ready to send and archive: totals computed, inconsistent input refused field by field, the official rule set cleared and the embedded XML re-read byte for byte. vat_treatment writes the reverse charge or intra-Community exemption mention.",
"serviceName": "Invoket"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"buyer": {
"name": "Agence Lumen SAS",
"vat_id": "FR23342663721",
"address": {
"city": "Paris",
"line1": "4 avenue du Parc",
"country": "FR",
"postal_code": "75011"
}
},
"lines": [
{
"qty": "1",
"vat": {
"rate": "20",
"category": "S"
},
"unit": "C62",
"unit_price": "1200.00",
"description": "Fabrication comptoir chene massif"
},
{
"qty": "6",
"vat": {
"rate": "20",
"category": "S"
},
"unit": "HUR",
"unit_price": "85.00",
"description": "Pose et finition sur site"
}
],
"seller": {
"name": "Menuiserie Dubois SARL",
"vat_id": "FR44732829320",
"address": {
"city": "Lyon",
"line1": "12 rue des Artisans",
"country": "FR",
"postal_code": "69003"
},
"legal_id": {
"value": "732829320",
"scheme": "0002"
}
},
"payment": {
"iban": "FR7630006000011234567890189",
"terms": "30 jours nets"
},
"currency": "EUR",
"due_date": "2026-08-11",
"issue_date": "2026-07-12",
"invoice_number": "FA-2026-0042"
},
"type": "http",
"method": "POST",
"schema": {
"type": "object",
"required": [
"buyer",
"currency",
"invoice_number",
"issue_date",
"lines",
"seller"
],
"properties": {
"buyer": {
"type": "object",
"required": [
"address",
"name"
],
"properties": {
"name": {
"type": "string"
},
"vat_id": {
"type": "string"
},
"address": {
"type": "object",
"required": [
"country"
],
"properties": {
"city": {
"type": "string"
},
"line1": {
"type": "string"
},
"country": {
"type": "string"
},
"postal_code": {
"type": "string"
}
}
}
}
},
"lines": {
"type": "array",
"items": {
"type": "object",
"required": [
"description",
"qty",
"unit",
"unit_price",
"vat"
],
"properties": {
"qty": {
"type": "string"
},
"vat": {
"type": "object",
"required": [
"category",
"rate"
],
"properties": {
"rate": {
"type": "string"
},
"category": {
"type": "string"
}
},
"description": "Line VAT: category (BT-151, UNTDID 5305: S standard, Z zero-rated, E exempt, AE reverse charge...), rate in percent (BT-152), and for exempt categories an exemption_reason (BT-120) carried onto the VAT breakdown - all EN 16931 VAT rules (BR-S/E/AE/Z...) are enforced, violations come back as 400 issues with their official BR ids"
},
"unit": {
"type": "string"
},
"unit_price": {
"type": "string"
},
"description": {
"type": "string"
}
}
},
"description": "Invoice lines (BG-25), required non-empty. Line ids (BT-126) are numbered for you; each line net (BT-131) is computed as qty x unit_price with the official EN 16931 rounding. Document totals (BG-22) and the VAT breakdown (BG-23) are computed from the lines; an optional top-level `totals` object is VERIFIED against that computation and rejected with code inconsistent_totals if it diverges - never silently repaired"
},
"seller": {
"type": "object",
"required": [
"address",
"name"
],
"properties": {
"name": {
"type": "string"
},
"vat_id": {
"type": "string"
},
"address": {
"type": "object",
"required": [
"country"
],
"properties": {
"city": {
"type": "string"
},
"line1": {
"type": "string"
},
"country": {
"type": "string"
},
"postal_code": {
"type": "string"
}
}
},
"legal_id": {
"type": "object",
"required": [
"value"
],
"properties": {
"value": {
"type": "string"
},
"scheme": {
"type": "string"
}
},
"description": "Optional. Seller legal registration identifier (BT-30): value plus optional ISO 6523 scheme (0002 SIREN). Syntax-checked (Luhn) like the VAT ids and the IBAN - an implausible identifier is rejected (400 with code implausible_identifier). To verify the party actually exists, use /company/resolve"
}
}
},
"payment": {
"type": "object",
"required": [],
"properties": {
"iban": {
"type": "string",
"description": "Optional. Payment IBAN (BT-84), becomes a credit-transfer payment instruction (BG-16, UNTDID 4461 code 30). Mod-97 checksum enforced. Optional payment.terms (BT-20)"
},
"terms": {
"type": "string"
}
}
},
"currency": {
"type": "string",
"description": "Invoice currency (BT-5), ISO 4217, required. It must be usable for billing: XXX (no currency) and XTS (test) are a 400 implausible_currency although BR-CL accepts them - a restriction no BR rule states; metals and units of account (XAU, XAG, XPD, XPT, XDR, XUA) are accepted"
},
"due_date": {
"type": "string"
},
"issue_date": {
"type": "string",
"description": "Issue date (BT-2), required, YYYY-MM-DD AND a real calendar date - 2026-13-99 fits the pattern but is a 400 invalid_date. Optional due_date (BT-9, same check) and type_code (BT-3, default 380 commercial invoice, 381 credit note)"
},
"invoice_number": {
"type": "string",
"description": "Invoice number (BT-1), required. The whole input is the simple business JSON shown here (identical to /invoice/generate) - unknown or misspelled fields are refused (400 INVALID_INVOICE_INPUT), a typo is never silently ignored. Max body 10 MB (413 beyond). A supplied electronic_address {value, scheme} is form-checked here too: a value repeating its own EAS code, or malformed for the declared scheme, is a 400 implausible_identifier"
}
}
},
"headers": {
"accept": "application/json",
"content-type": "application/json"
},
"bodyType": "json"
},
"output": {
"type": "json",
"schema": {
"type": "object",
"required": [
"data",
"provenance"
],
"properties": {
"data": {
"type": "object",
"required": [
"computed",
"pdf_base64",
"profile",
"validated",
"xml"
],
"properties": {
"xml": {
"type": "string",
"description": "The embedded CII D16B XML served flat too, so the agent need not re-extract it - identical byte-for-byte to the XML inside the PDF, and guaranteed conformant: before being served the whole document is re-validated by the service's own EN 16931 engine (the four layers of /invoice/validate) AND its embedded XML is re-read by our own reader (F-002) and compared byte-for-byte. Any post-condition miss is a 500 - never served, never charged"
},
"profile": {
"type": "string",
"description": "Profile URN emitted in the embedded XML's BT-24: always urn:cen.eu:en16931:2017 (Factur-X EN 16931) in v1 - the legal core of the French 2026-2027 reform. UBL output and national CIUS (XRechnung) are out of scope"
},
"computed": {
"type": "object",
"required": [
"totals",
"vat_breakdown"
],
"properties": {
"totals": {
"type": "object",
"required": [
"due",
"grand_total",
"lines_net",
"net",
"vat_total"
],
"properties": {
"due": {
"type": "string"
},
"net": {
"type": "string"
},
"lines_net": {
"type": "string"
},
"vat_total": {
"type": "string"
},
"grand_total": {
"type": "string"
}
}
},
"vat_breakdown": {
"type": "array",
"items": {
"type": "object",
"required": [
"category",
"rate",
"tax_amount",
"taxable_amount"
],
"properties": {
"rate": {
"type": "string"
},
"category": {
"type": "string"
},
"tax_amount": {
"type": "string"
},
"taxable_amount": {
"type": "string"
}
}
}
}
},
"description": "The totals (BG-22) and VAT breakdown (BG-23) actually serialized in the XML, restated for agent re-reading: computed from the lines when not provided, verified when provided. Amounts are exact decimal strings"
},
"validated": {
"type": "boolean",
"description": "Post-condition echo: always true on a 200 (generated-then-validated AND embedded-XML re-read byte-for-byte)"
},
"pdf_base64": {
"type": "string",
"description": "The complete Factur-X document, base64-encoded (standard alphabet): a PDF/A-3B file (human-readable, proven veraPDF-green) with the EN 16931 CII XML embedded plus its XMP metadata - the hybrid invoice the French 2026-2027 reform mandates. Decode it client-side to get the PDF bytes. Truncated in this discovery example to keep the 402 challenge header small; the real response carries it in full"
},
"vat_treatment": {
"type": "object"
}
}
},
"provenance": {
"type": "object",
"required": [
"fetched_at",
"freshness",
"source"
],
"properties": {
"source": {
"type": "string"
},
"freshness": {
"type": "object",
"required": [
"as_of",
"kind"
],
"properties": {
"kind": {
"type": "string"
},
"as_of": {
"type": "string"
}
}
},
"fetched_at": {
"type": "string"
}
}
}
}
},
"example": {
"data": {
"xml": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<rsm:CrossIndustryInvoice xmlns:rsm=\"urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100\" xmlns:ram=\"urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100\" xmlns:qdt=\"urn:un:unece:uncefact:data:standard:QualifiedDataType:100\" xmlns:udt=\"urn:un:unece:uncefact:data:standard:UnqualifiedDataType:100\">\n <rsm:ExchangedDocumentContext>\n <ram:GuidelineSpecifiedDocumentContextParameter>\n <ram:ID>urn:cen.eu:en16931:2017</ram:ID>\n </ram:GuidelineSpecifiedDocumentContextParameter>\n </rsm:ExchangedDocumentContext>\n <rsm:ExchangedDocument>\n <ram:ID>FA-2026-0042</ram:ID>\n <ram:TypeCode>380</ram:TypeCode>\n <ram:IssueDateTime>\n <udt:DateTimeString format=\"102\">20260712</udt:DateTimeString>\n </ram:IssueDateTime>\n </rsm:ExchangedDocument>\n <!-- SupplyChainTradeTransaction (two BG-25 line items, parties, VAT S 20%,\n payment IBAN, monetary summation grand total 2052) elided for brevity —\n identical byte-for-byte to /invoice/generate; also embedded in the PDF -->\n</rsm:CrossIndustryInvoice>\n",
"profile": "urn:cen.eu:en16931:2017",
"computed": {
"totals": {
"due": "2052",
"net": "1710",
"lines_net": "1710",
"vat_total": "342",
"grand_total": "2052"
},
"vat_breakdown": [
{
"rate": "20",
"category": "S",
"tax_amount": "342",
"taxable_amount": "1710"
}
]
},
"validated": true,
"pdf_base64": "JVBERi0xLjcKJYCAgIAKMSAwIG9iago8PC9UeXBlL1BhZ2VzL0NvdW50IDEvS2lkc1s5IDAgUl0+PgplbmRvYmoKMiAwIG9iago8PC9UeXBlL091dHB1dEludGVudC9E …[base64 truncated for the 402 header budget — full response is 34108 base64 chars = a 25 580-byte PDF/A-3B, veraPDF-green; decode client-side]"
},
"provenance": {
"source": "en16931-artefacts",
"freshness": {
"kind": "snapshot",
"as_of": "2026-07-13T00:00:00Z"
},
"fetched_at": "2026-07-13T15:16:33Z"
}
}
}
},
"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",
"required": [
"buyer",
"currency",
"invoice_number",
"issue_date",
"lines",
"seller"
],
"properties": {
"buyer": {
"type": "object",
"required": [
"address",
"name"
],
"properties": {
"name": {
"type": "string"
},
"vat_id": {
"type": "string"
},
"address": {
"type": "object",
"required": [
"country"
],
"properties": {
"city": {
"type": "string"
},
"line1": {
"type": "string"
},
"country": {
"type": "string"
},
"postal_code": {
"type": "string"
}
}
}
}
},
"lines": {
"type": "array",
"items": {
"type": "object",
"required": [
"description",
"qty",
"unit",
"unit_price",
"vat"
],
"properties": {
"qty": {
"type": "string"
},
"vat": {
"type": "object",
"required": [
"category",
"rate"
],
"properties": {
"rate": {
"type": "string"
},
"category": {
"type": "string"
}
},
"description": "Line VAT: category (BT-151, UNTDID 5305: S standard, Z zero-rated, E exempt, AE reverse charge...), rate in percent (BT-152), and for exempt categories an exemption_reason (BT-120) carried onto the VAT breakdown - all EN 16931 VAT rules (BR-S/E/AE/Z...) are enforced, violations come back as 400 issues with their official BR ids"
},
"unit": {
"type": "string"
},
"unit_price": {
"type": "string"
},
"description": {
"type": "string"
}
}
},
"description": "Invoice lines (BG-25), required non-empty. Line ids (BT-126) are numbered for you; each line net (BT-131) is computed as qty x unit_price with the official EN 16931 rounding. Document totals (BG-22) and the VAT breakdown (BG-23) are computed from the lines; an optional top-level `totals` object is VERIFIED against that computation and rejected with code inconsistent_totals if it diverges - never silently repaired"
},
"seller": {
"type": "object",
"required": [
"address",
"name"
],
"properties": {
"name": {
"type": "string"
},
"vat_id": {
"type": "string"
},
"address": {
"type": "object",
"required": [
"country"
],
"properties": {
"city": {
"type": "string"
},
"line1": {
"type": "string"
},
"country": {
"type": "string"
},
"postal_code": {
"type": "string"
}
}
},
"legal_id": {
"type": "object",
"required": [
"value"
],
"properties": {
"value": {
"type": "string"
},
"scheme": {
"type": "string"
}
},
"description": "Optional. Seller legal registration identifier (BT-30): value plus optional ISO 6523 scheme (0002 SIREN). Syntax-checked (Luhn) like the VAT ids and the IBAN - an implausible identifier is rejected (400 with code implausible_identifier). To verify the party actually exists, use /company/resolve"
}
}
},
"payment": {
"type": "object",
"required": [],
"properties": {
"iban": {
"type": "string",
"description": "Optional. Payment IBAN (BT-84), becomes a credit-transfer payment instruction (BG-16, UNTDID 4461 code 30). Mod-97 checksum enforced. Optional payment.terms (BT-20)"
},
"terms": {
"type": "string"
}
}
},
"currency": {
"type": "string",
"description": "Invoice currency (BT-5), ISO 4217, required. It must be usable for billing: XXX (no currency) and XTS (test) are a 400 implausible_currency although BR-CL accepts them - a restriction no BR rule states; metals and units of account (XAU, XAG, XPD, XPT, XDR, XUA) are accepted"
},
"due_date": {
"type": "string"
},
"issue_date": {
"type": "string",
"description": "Issue date (BT-2), required, YYYY-MM-DD AND a real calendar date - 2026-13-99 fits the pattern but is a 400 invalid_date. Optional due_date (BT-9, same check) and type_code (BT-3, default 380 commercial invoice, 381 credit note)"
},
"invoice_number": {
"type": "string",
"description": "Invoice number (BT-1), required. The whole input is the simple business JSON shown here (identical to /invoice/generate) - unknown or misspelled fields are refused (400 INVALID_INVOICE_INPUT), a typo is never silently ignored. Max body 10 MB (413 beyond). A supplied electronic_address {value, scheme} is form-checked here too: a value repeating its own EAS code, or malformed for the declared scheme, is a 400 implausible_identifier"
}
}
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"schema": {
"type": "object"
},
"headers": {
"type": "object",
"additionalProperties": {
"type": "string"
}
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
},
"queryParams": {
"type": "object",
"additionalProperties": {
"type": "string"
}
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
},
"x402Version": 2
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.1 USDC on Base to 0x4465…128ee. The signed payment is good for 1 minute.
- Paid to
- 0x4465…128ee
- USD Coin contract
- 0x8335…02913
- Payment window
- 1 minute
- As published
- 100000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x4465825B0ac713aA2Fa07Ea29023020804A128ee",
"amount": "100000",
"scheme": "exact",
"network": "eip155:8453",
"resource": "https://api.invoket.com/invoice/generate-pdf",
"maxTimeoutSeconds": 60
}
]Provenance
- Seen in the source catalog
- 2026-09-23 19:43Z
- Last indexed by Roundhouse
- 2026-09-24 11:15Z
- Last enriched (probe, favicon, geo)
- 2026-09-16 20:45Z
- x402 version
- 2
- Max timeout
- 60s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 22 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service api.invoket.com and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=api.invoket.com' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.invoket.com/invoice/generate-pdf, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.