Temlavo website screenshot

Temlavo

Temlavo provides an Invoice Extraction API that transforms invoice PDFs and images into structured JSON accounting data. The service extracts line items, performs consistency checks, flags duplicate signals, and supplies explicit review outcomes. It aims to streamline automation workflows for developers handling financial documents.

Temlavo publishes 2 API contracts indexed on the APIs.io network: Documents API and Usage API. Tagged areas include Company, Invoices, Extraction, and Accounting.

Temlavo’s developer surface includes API reference, documentation, pricing, support, signup flow, and 14 more developer resources.

🌐 Visit website📡 Profile data on GitHub
46.1/100 developing ▲ 16.6 Agent 36/100 agent ready Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0
1 published contract
CompanyInvoicesExtractionAccounting

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0
Composite quality — 46.1/100 · developing
Contract Quality 9.5 / 19
Developer Ergonomics 5.7 / 15
Access Clarity 11.4 / 15
Operational Transparency 1.0 / 10
Contract Governance 0.0 / 9
Discoverability 4.8 / 8
Regulatory Posture 2.9 / 15
Create-or-Update Ergonomics 2.8 / 10
Agent readiness — 36/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/temlavo: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Temlavo Documents API

Invoice document operations of the Temlavo Invoice Extraction API (OpenAPI 3.1, version 1.0.0) — create an invoice document and receive an upload authorization, confirm a direct...

Temlavo Usage API

Usage operation of the Temlavo Invoice Extraction API — retrieve current or historical processing usage for the account. Bearer API key authentication.

Pricing Plans 1

Published pricing tiers and plan structures.

Temlavo Plans Pricing

3 plans

PLANS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Temlavo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Temlavo Vulnerability Disclosure

no policy recorded

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 SignUp
SignUp
 Login
Login

Documentation 2

Reference material describing how the API behaves

APIReference
APIReference
 Documentation
Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt

Build 2

SDKs, sample code, and the tooling you integrate with

Packages
Packages
 SDKs
SDKs

Access & Security 3

Authentication, authorization, and security posture

Security
Security
 VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support
Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans
Plans
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Pricing
Pricing

Company 1

The organization behind the API

Website
Website

Other 2

Properties that don't map to a standard resource type

Hosts
Hosts
 Vendors
Vendors

Source (apis.yml)

apis.yml Raw ↑ 
aid: temlavo
name: Temlavo
image: https://temlavo.com/opengraph-image-1c1a04?1ecd09803a86c066
description: Temlavo provides an Invoice Extraction API that transforms invoice PDFs and images into structured JSON accounting
  data. The service extracts line items, performs consistency checks, flags duplicate signals, and supplies explicit review
  outcomes. It aims to streamline automation workflows for developers handling financial documents.
url: https://raw.githubusercontent.com/api-evangelist/temlavo/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-02 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-02'
modified: '2026-10-05'
tags:
- Company
- Invoices
- Extraction
- Accounting
tags_raw:
- Company
- Invoice
- Extraction
- API
- Accounting
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/temlavo-plans-pricing.yml
- type: Security
  url: security/temlavo-vulnerability-disclosure.yml
- type: LLMsTxt
  url: llms/temlavo-llms.txt
- type: Hosts
  url: hosts/temlavo-hosts.yml
- type: Vendors
  url: vendors/temlavo-vendors.yml
- type: Packages
  url: packages/temlavo-packages.yml
- type: TermsOfService
  url: https://temlavo.com/terms
- type: SDKs
  url: https://www.npmjs.com/package/@temlavo/sdk
- type: PrivacyPolicy
  url: https://temlavo.com/privacy
- type: APIReference
  url: https://temlavo.com/docs/api-reference
- type: VulnerabilityDisclosure
  url: security/temlavo-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/temlavo-domain-security.yml
- type: Website
  url: https://temlavo.com
- type: Documentation
  url: https://temlavo.com/docs
- type: DeveloperPortal
  url: https://temlavo.com/playground
- type: Pricing
  url: https://temlavo.com/pricing
- type: Support
  url: https://temlavo.com/security
- type: SignUp
  url: https://temlavo.com/sign-up
- type: Login
  url: https://temlavo.com/sign-in
apis:
- aid: temlavo:temlavo-documents-api
  name: Temlavo Documents API
  description: Invoice document operations of the Temlavo Invoice Extraction API (OpenAPI 3.1, version 1.0.0) — create an
    invoice document and receive an upload authorization, confirm a direct upload so it is admitted for processing, retrieve
    the document resource with its extracted data, consistency checks and duplicate signals, and delete a document with its
    retained customer content. Bearer API key authentication.
  humanURL: https://temlavo.com/docs
  baseURL: https://api.temlavo.com
  tags:
  - Documents
  properties:
  - type: OpenAPI
    url: openapi/temlavo-documents-api-openapi.yml
  - type: OpenAPI
    name: OpenAPI (provider-hosted, docs host)
    url: https://temlavo.com/openapi.json
  - type: Documentation
    url: https://temlavo.com/docs
  - type: APIReference
    url: https://temlavo.com/docs/api-reference
  - type: JSONSchema
    name: Invoice JSON Schema (invoice.v1)
    url: https://temlavo.com/schemas/invoice.v1.json
- aid: temlavo:temlavo-usage-api
  name: Temlavo Usage API
  description: Usage operation of the Temlavo Invoice Extraction API — retrieve current or historical processing usage for
    the account. Bearer API key authentication.
  humanURL: https://temlavo.com/docs
  baseURL: https://api.temlavo.com
  tags:
  - Usage
  properties:
  - type: OpenAPI
    url: openapi/temlavo-usage-api-openapi.yml
  - type: OpenAPI
    name: OpenAPI (provider-hosted, docs host)
    url: https://temlavo.com/openapi.json
  - type: Documentation
    url: https://temlavo.com/docs
  - type: APIReference
    url: https://temlavo.com/docs/api-reference
x-submission-notes: Invoice extraction API turning invoice PDFs/images into accounting data.
x-submission-probe: root 200; docs 200; OpenAPI 3.1.0 4 paths server api.temlavo.com; llms.txt 200; 404 probe 404
x-submitted-by: marketing@temlavo.com (apis.io/add, 2026-10-02)
x-coverage:
  state: covered
  reason: contract-on-docs-host
  detail: The OpenAPI 3.1.0 contract (4 paths, 5 operations) is published on the docs host at https://temlavo.com/openapi.json
    and declares the runtime server https://api.temlavo.com. The earlier unreadable state came from looking for the contract
    on the API runtime host; corrected at the provider's request (api-evangelist/temlavo#1).
  evidence:
  - url: https://temlavo.com/openapi.json
    status: 200
  - url: https://temlavo.com/schemas/invoice.v1.json
    status: 200
  checked: '2026-10-05'
x-enrichment:
  date: '2026-10-02'
  status: enriched
  artifacts_added: 9
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local
x-correction-request:
  requested: '2026-10-05'
  source:
  - https://github.com/api-evangelist/temlavo/issues/1
  request: 'Issue #1 (stefanoskalt), verified live 2026-10-05. https://temlavo.com/openapi.json returns 200 application/json:
    OpenAPI 3.1.0, "Temlavo Invoice Extraction API" version 1.0.0, server https://api.temlavo.com, 4 paths and 5 operations
    (createDocument, completeDocumentUpload, getDocument, deleteDocument, getUsage), bearer API key security, no tags. https://temlavo.com/docs,
    https://temlavo.com/docs/api-reference, https://temlavo.com/schemas/invoice.v1.json and https://temlavo.com/llms.txt all
    return 200; an invented /docs path returns a real 404. https://api.temlavo.com/ returns 200 with an empty body (it also
    answers 200 on an invented path, so the runtime host is not a document source). Associate the docs-host OpenAPI with the
    Temlavo API entry.'
  applied: '2026-10-05'
  applied_note: Saved https://temlavo.com/openapi.json verbatim as openapi/_original/temlavo-openapi.json and split it (operations
    untagged, so grouped by path) into openapi/temlavo-documents-api-openapi.yml (4 operations) and openapi/temlavo-usage-api-openapi.yml
    (1 operation), registered as two API entries with baseURL https://api.temlavo.com and the provider-hosted OpenAPI, docs,
    API reference and invoice JSON Schema as properties. x-coverage moved from unreadable to covered. Scoring reruns on the
    next scheduled pass.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/temlavo"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/temlavo/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/temlavo/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.