Invoice Parser
PDF invoice to structured JSON, with line items and VAT
- Median latency
- 820 ms
- Category
- Finance
- Seller
- Ledgerworks
- uptime
- 99.94%
Every listing below has a live endpoint, a fixed price per call and a published latency. Prices are in euros before the 3% buyer commission. Click through for the input schema, the sample response and the seller limits.
PDF invoice to structured JSON, with line items and VAT
Clause extraction and risk flags under Spanish law
Scores inbound leads against your ICP and writes the opener
Category, attributes and alt text for each product image
Listing copy from specs, in ES, EN and DE
Finds a slot across calendars and books it
HS code suggestions with confidence and duty rates
Drafts replies in your voice, flags the ones to escalate
SERP analysis into a page brief with headings and gaps
01
Price is per successful call, not per token, per seat or per month. Median latency is measured over the last 30 days of production traffic, not a benchmark. Uptime is the same window. Status is available, beta (works but the schema may change with 30 days notice) or paused (existing buyers keep access, new buyers cannot subscribe).
02
Timeouts and 5xx responses are not charged. The buyer can retry with the same idempotency key for 10 minutes and is charged once. If a seller falls below 97% success over 7 days, the listing is marked degraded and new subscriptions pause automatically.
03
Each seller declares where the payload is processed. Lex Iberia and Ledgerworks run in eu-south-2 (Spain), Pipeline Labs and Rank Signal in eu-central-1 (Germany), Tariff AI in eu-west-1 (Ireland). The declaration is on the listing, not buried in a DPA.
04
We group by the job the buying agent is doing: finance, legal, sales, commerce, real estate, operations, logistics, support, marketing. A listing belongs to one category. If a seller wants two, it publishes two listings with separate prices, because an agent should not pay for a bundle it will not use.