What authentication does the Paigo API use?

Paigo uses OAuth 2.0 client-credentials. You POST your `client_id` and `client_secret` to `https://auth.paigo.tech/oauth/token` with the audience set to the Paigo API gateway, receive a JWT bearer token valid for 24 hours, and attach it as `Authorization: Bearer <token>` on every API call. Jentic handles the token exchange and refresh so agents never see the client secret.

Can I ingest usage events with the Paigo API?

Yes - POST /usage is the primary ingestion endpoint. You send usage events tied to a customer and a dimension (defined under /dimensions). Paigo aggregates the events according to the offering's pricing rules and emits invoices on the configured cadence. For backfills, send historical events in batches rather than per-event.

What are the rate limits for the Paigo API?

Paigo does not publish fixed rate limits in the public spec. Treat /usage as the high-volume endpoint and batch events into single calls where possible. If you receive a 429 response, back off and retry - Paigo returns a Retry-After header on throttled responses.

How do I create a usage-based pricing model through Jentic?

Run `pip install jentic`, search for 'create a Paigo dimension', then for 'create a Paigo offering'. Create the dimension first (for example 'api_calls'), then the offering that prices it. Finally, search for 'ingest Paigo usage events' and call POST /usage as customers consume the metered resource. The OAuth token is handled by Jentic on every call.

Can I model parent-child customer relationships?

Yes - POST /customers/{customerId}/children/{childId} attaches a child to a parent so usage rolls up the hierarchy. PUT updates the relationship metadata and DELETE detaches the child. This is the right primitive when an enterprise customer wants a single invoice that covers multiple subsidiaries.

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

Yes. Because you run Jentic One yourself, you decide which Paigo operations your agent may call, so a destructive one like issuing a refund via POST /customers/{customerId}/refunds is left out unless you add it. Paigo carries the customer id in the URL path, so for nested operations such as POST /customers/{customerId}/children/{childId} and the refund endpoint you can pin your agent to a single customer. The OAuth token stays with your own instance and is injected at execution, so the agent only ever exercises the operations and credentials your rules permit.