Install Jentic One Beta

Connect the Lago API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lago API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetlago.com%2Fgetlago" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetlago.com%2Fgetlago" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Lago API.

Create and update customers that billing and usage attach to

Send single usage events that feed metered pricing in real time

Send batches of usage events in one call for high-volume metering

Assign a plan to a customer to start a subscription

List subscriptions and the invoices Lago generates from metered usage

GET STARTED

Start building with Lago API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Lago API for, with concrete tasks.

★ Agent-managed usage metering

An AI agent reconciling product usage can call the Lago API through Jentic to create the customer if needed, stream usage events as the product is consumed, and list the resulting invoices to confirm the charge. Jentic returns the usage-event operation from a natural-language query, so the agent meters consumption without reading the Lago reference first.

Create or update the customer, send a usage event recording the consumed quantity, then list the customer's invoices to confirm the charge landed.

Subscription provisioning

Assign a plan to a customer to start a subscription when they upgrade, and keep the customer record current as their details change. Lago turns the subscription and any metered events into invoices, so a provisioning workflow only needs to manage customers, plans, and events.

Create the customer, assign the chosen plan as a subscription, and confirm the subscription appears in the customer's subscription list.

High-volume event batching

Collect usage events from a metering pipeline and send them to Lago in batches rather than one call per event, which keeps high-volume metering efficient. The batch events operation accepts many events at once, and the resulting charges roll into the customer's invoices.

Buffer the usage events collected over the interval and send them in a single batch events call, then verify the count accepted.

Key Endpoints

8 endpoints — the lago api meters usage and runs recurring billing for subscription and usage-based products.

METHOD

PATH

DESCRIPTION

GET

/customers

List all customers

POST

/customers

Create or update a customer

GET

/customers/{external_customer_id}

Retrieve a customer by external id

POST

/events

Send a usage event

POST

/events/batch

Send a batch of usage events

GET

/subscriptions

List subscriptions

POST

/subscriptions

Assign a plan to a customer

GET

/invoices

List invoices

GET

/customers

List all customers

POST

/customers

Create or update a customer

GET

/customers/{external_customer_id}

Retrieve a customer by external id

POST

/events

Send a usage event

POST

/events/batch

Send a batch of usage events

GET

/subscriptions

List subscriptions

POST

/subscriptions

Assign a plan to a customer

GET

/invoices

List invoices

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Lago API by hand means handling its bearer token, choosing the global or EU host to match where your data lives, and coding the event ingestion and subscription calls yourself. Through Jentic you install once, import the API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Lago carries the customer external id in the URL path for customer retrieval, but usage events and subscriptions target resources through the request body, so bound your agent to the operations it needs. You choose which operations it may call, so subscription assignment is not included unless you add it.

Credential isolation

Your Lago token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a usage event' or 'list invoices', and Jentic returns the matching Lago operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Lago API through Jentic.

Is there a Lago API MCP server?

You do not need an MCP server to give your agent the Lago API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the customer, event, subscription, and invoice operations. Operations are discovered on demand, so no extra server definitions load into the agent's context.

What authentication does the Lago API use?

The API authenticates with a bearer token per its OpenAPI spec, sent in the Authorization header on every billing call. Through Jentic the token is stored encrypted in your own Jentic One instance and supplied only when an allowed call runs, so it never reaches the agent's context.

Does the Lago API offer separate EU and US hosts?

Yes. The spec lists a global host at api.getlago.com and an EU-resident host at api.eu.getlago.com. Call the host that matches where your Lago data lives so usage events reach the right region.

What are the rate limits for the Lago API?

The OpenAPI spec does not specify rate limits. Lago announces changes through versioned migration guides, so confirm the current limits for your plan in the Lago documentation at https://doc.getlago.com.

Can I limit what my agent is allowed to do with the Lago API?

Yes. Write a rule that permits only the event and read operations, sending usage events and listing invoices, when the agent should meter and report, and add customer creation or subscription assignment only for provisioning workflows, with every call logged.

How do I send a usage event with the Lago API through Jentic?

Search Jentic for 'send a usage event for billing' to surface the event operation, load its input schema, pass the customer external id and metered quantity, and execute. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Getlago Lago API

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsBilling Subscriptionsbearer8 EndpointsREST

For Agents

Run usage-based and subscription billing with Lago: create customers, send single or batched usage events, assign plans as subscriptions, and list generated invoices.

Use for: Create a new customer for billing, Send a usage event to meter a customer's consumption, Send a batch of usage events collected over an hour, Assign a pricing plan to a customer as a subscription

Not supported: Does not handle payment capture, tax filing, or accounting ledgers. Use for usage metering, subscriptions, and invoice generation only.

The Lago API meters usage and runs recurring billing for subscription and usage-based products. It creates and updates customers, ingests single or batched usage events that feed metered pricing, assigns plans to customers as subscriptions, and lists the invoices Lago generates from that usage. This agent-friendly profile covers the common billing operations; Lago publishes the full description separately. It is aimed at teams building metered or hybrid pricing that need programmatic control over customers, events, subscriptions, and invoices.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

65%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

86%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Lago API to your agent

Capabilities

Start building with Lago API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Getlago Lago API

Jentic AI Readiness Score

Lago API — agent discovery profile

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness