Pennylane
Pennylane is a French financial and accounting operating system for SMEs and accounting firms. The Company API (v2) lets companies, firms, and integration partners access and sync invoicing, accounting, banking, and financial data over a REST interface, and automate end-to-end workflows. V2 is the stable version; V1 is deprecated. All amounts are in EUR and the platform is built around French accounting (FEC exports, Plateforme Agréée e-invoicing, SEPA/GoCardless mandates).
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Pennylane the way a machine reads it — 29 machine-readable artifacts across 19 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Pennylane scores 68.9/100 (strong), with a separate agent-readiness read of 79/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Pennylane
Each block below is one kind of artifact we hold for Pennylane. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Pennylane Account API
The Account API from Pennylane — 1 operation(s) for account.
Pennylane Accounting Exports API
The Accounting Exports API from Pennylane — 2 operation(s) for accounting exports.
Pennylane Bank Accounts API
The Bank Accounts API from Pennylane — 2 operation(s) for bank accounts.
Pennylane Billing Subscriptions API
The Billing Subscriptions API from Pennylane — 1 operation(s) for billing subscriptions.
Pennylane Categories API
The Categories API from Pennylane — 2 operation(s) for categories.
Pennylane Change Events API
The Change Events API from Pennylane — 2 operation(s) for change events.
Pennylane Customer Invoices API
The Customer Invoices API from Pennylane — 7 operation(s) for customer invoices.
Pennylane Customers API
The Customers API from Pennylane — 4 operation(s) for customers.
Pennylane E-Invoicing API
The E-Invoicing API from Pennylane — 1 operation(s) for e-invoicing.
Pennylane File Attachments API
The File Attachments API from Pennylane — 1 operation(s) for file attachments.
Pennylane Journals API
The Journals API from Pennylane — 2 operation(s) for journals.
Pennylane Ledger Accounts API
The Ledger Accounts API from Pennylane — 2 operation(s) for ledger accounts.
Pennylane Ledger Entries API
The Ledger Entries API from Pennylane — 4 operation(s) for ledger entries.
Pennylane Mandates API
The Mandates API from Pennylane — 2 operation(s) for mandates.
Pennylane Products API
The Products API from Pennylane — 2 operation(s) for products.
Pennylane Quotes API
The Quotes API from Pennylane — 2 operation(s) for quotes.
Pennylane Supplier Invoices API
The Supplier Invoices API from Pennylane — 4 operation(s) for supplier invoices.
Pennylane Suppliers API
The Suppliers API from Pennylane — 2 operation(s) for suppliers.
Pennylane Transactions API
The Transactions API from Pennylane — 2 operation(s) for transactions.
Scroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
pennylane-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Pennylane Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Pennylane Finops
FINOPSSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Pennylane — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/pennylane · machine-readable index on apis.io