Build an integration that stops at the invoice draft
Use exact monetary strings, scoped HTTP access and retry protection, then hand the draft to a person.
The working library
Developer notes on the released draft API, application source, customization and maintaining a licensed installation.
Developer notes on the released draft API, application source, customization and maintaining a licensed installation.
Use exact monetary strings, scoped HTTP access and retry protection, then hand the draft to a person.
Plan source changes around the licensed installation, exact financial actions, stored originals and a repeatable update process.
Use the optional MCP and HTTP tools to prepare invoice drafts, explain overdue balances or read customer context. You confirm invoice issuance. You can also maintain a source change for a licensed installation. Both need the same care around permissions, exact amounts and stored document evidence.
The Agent API category separates connection setup, jobs, permissions, tool inputs, retries and exclusions into guides you can extend with your integration. The tested-client table records exact versions. No embedded model provider is required.
The guides below define the supported integration boundary and the maintenance work that source access brings. The technical manual covers the package and runtime; the connection guide explains access and approval.
The manual covers installation, daily work and maintenance.
Open the documentationWriting about Pepper? The affiliate program includes a media kit and ready-to-use copy.