FA
Payments · x402 · early usage

Peppol e-invoicing lookup: participant id and accepted documents

Peppol e-invoicing lookup: participant id and accepted documents. Use when you need to send an e-invoice or check if a company can receive one: looks the company up in the Peppol Directory by VAT number, company number (Belgian KBO, French SIREN, Dutch KvK...…

by factline.dev · discovered, not yet claimed by its owner · updated 2026-10-12

30d calls2
30d payers2
MethodGET
Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Peppol e-invoicing lookup: participant id and accepted documents. Use when you need to send an e-invoice or check if a company can receive one: looks the company up in the Peppol Directory by VAT number, company number (Belgian KBO, French SIREN, Dutch KvK...) or name, and returns its Peppol participant ids and accepted documents (invoice, credit note, self-billing, orders). Belgium requires Peppol B2B e-invoicing since 2026; France requires e-invoice receipt from 2026-09.

Tags: peppol · e-invoicing · einvoice · invoice · accounts-payable · bazaar · payment-identifier

Call contract

Method
GET
Input
query parameters
Output
json
Last paid call
2026-10-12
Input example from Bazaar metadata
{
  "vat": "BE0400378485"
}
Output example
{
  "can_receive_invoices": true,
  "explain": {
    "mandates": "Peppol B2B e-invoicing is required in Belgium since 2026-01-01. France requires all companies to receive e-invoices from 2026-09-01 (via certified platforms; 0225 ids are French e-invoicing addresses). Germany requires all companies to receive e-invoices since 2025.",
    "name_search": "A name search returns participants whose registered name matches; check the VAT or company number before sending.",
    "not_found": "Not in the Peppol Directory. New registrations can take up to a day to appear, and some access points do not publish to the directory, so this is not proof the company cannot receive Peppol invoices. Ask the company for its Peppol id.",
    "on_peppol": "The company is registered as a receiver on the Peppol network (via a certified access point), so you can send it e-invoices over Peppol using any of the participant ids."
  },
  "more_results": 0,
  "on_peppol": true,
  "participants": [
    {
      "accepts": [
        "invoice",
        "credit note"
      ],
      "can_receive_invoices": true,
      "country": "BE",
      "name": "Colruyt Group NV",
      "other_ids": [],
      "participant_id": "0208:0400378485",
      "registered": "2023-08-30",
      "scheme": "Belgian company number (KBO/BCE)"
    },
    {
      "accepts": [
        "invoice",
        "credit note"
      ],
      "can_receive_invoices": true,
      "country": "BE",
      "name": "Colruyt Group NV",
      "other_ids": [
        "0208:0400378485"
      ],
      "participant_id": "9925:be0400378485",
      "registered": "2022-04-22",
      "scheme": "Belgian VAT"
    }
  ],
  "query": {
    "by": "vat",
    "country": "BE",
    "value": "BE0400378485"
  },
  "source": "Peppol Directory (OpenPeppol)"
}

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/34891.json for the price and payment options.
  3. Pay. Call GET https://factline.dev/v1/einvoice/peppol. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, Solana, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.003 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base, Solana
Demand
2 calls · 2 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.0030xb58dd178abac67f6d4894437a7fc725cbddb2075120s
exactSolana
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
USDC$0.003fyqifu7otDYanhqr84B9YzZfA5LwRTJ1uFLqDJinMTK120s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0xb58dd178abac67f6d4894437a7fc725cbddb2075",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "3000",
    "amountUsd": 0.003,
    "maxTimeoutSeconds": 120
  },
  {
    "scheme": "exact",
    "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
    "payTo": "fyqifu7otDYanhqr84B9YzZfA5LwRTJ1uFLqDJinMTK",
    "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "3000",
    "amountUsd": 0.003,
    "maxTimeoutSeconds": 120
  }
]

Schemas

Output schema (JSON Schema)
{
  "properties": {
    "example": {
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}
Example shape — generated from the schema, not a captured live response
{
  "example": {},
  "type": "string"
}

Examples

curl
curl "https://factline.dev/v1/einvoice/peppol"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://factline.dev/v1/einvoice/peppol");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://factline.dev/v1/einvoice/peppol")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
factline.dev
Endpoint
https://factline.dev/v1/einvoice/peppol
Machine-readable
/resources/34891.json