API-first invoicing

Invoices your agents can actually run.

Billtyme gives agents a narrow, typed command surface for customer and invoice workflows—with durable state, safe retries, and no dashboard dependency.

Read the docs Explore the API

OpenAPI 3.1
WorkOS-ready
Postgres-backed

invoice.http

POST /v1/companies/0198…0001/invoices
Authorization: Bearer <token>
Idempotency-Key: invoice-acme-2026-08

{
  "customer_id": "…",
  "currency": "EUR",
  "issue_date": "2026-08-11",
  "due_date": "2026-08-25",
  "lines": [
    {
      "description": "Consulting",
      "quantity": "8",
      "unit_amount_minor": 15000,
      "tax_rate_bps": 1900
    }
  ]
}

201 Createddraft persisted

Built for delegation

A billing core, not another screen to manage.

Agents use the same explicit commands a human integration would. Every mutation is validated, tenant-scoped, and safe to retry.

Agent-native

Everything important is available through a typed HTTP contract.

Safe by default

WorkOS identity, account isolation, company boundaries, permissions, and idempotency.

Ready to become a product

Operations, Slack, and future MCP clients share one billing system of record.

One durable core

HTTP first. MCP next. Same commands underneath.

Billtyme stays independent of the channel that invokes it. The API is the product boundary; agent experiences remain replaceable adapters.

Read the product notes See every release

Agent channels

SkillSail Operations plannedSlack agent plannedMCP clients planned

Billtyme APIHono + OpenAPI

Durable state

PlanetScale PostgresR2 PDF artifacts nextAudit history

Early foundation

Start with the API. Add the agent surface when the commands are solid.

Open API reference