Reeve.Credits

What it does

• By default, your app doesn't have access to the credits feature—the app owner needs to turn it on first through a simple request. Once enabled, your app can use credits by including a secure secret key with each request; using a public key or missing the key will be rejected for security reasons.

Getting started

1. Have the app owner request the credits capability for your host app. It is not on by default.
2. Authenticate with your secret Reeve host key (X-Reeve-Host-Key) to call the Reeve.Credits surface; a public key or a missing key is rejected.
3. Make your first request and check the response, then wire it into your app.

Limits & notes

• Usage is metered against your Reeve credit balance via credits_ledger_entry; see the pricing page for current rates.
• Requests authorize on your organization; a valid host key scoped to this capability is required.

FAQ

What does Reeve.Credits do?

By default, your app doesn't have access to the credits feature—the app owner needs to turn it on first through a simple request. Once enabled, your app can use credits by including a secure secret key with each request; using a public key or missing the key will be rejected for security reasons.

How is Reeve.Credits billed?

Usage is metered against your Reeve credit balance; see the pricing page for rates.

Sources

2 of 9 claims on this page are grounded in the Reeve.Knowledge product corpus. The rest are product/catalog reference copy with no Knowledge card behind them, listed as uncited below.

• does.0 — [source]
• faqs.0.a — [source]
• overview — uncited (reference copy)
• how_to.0 — uncited (reference copy)
• how_to.1 — uncited (reference copy)
• how_to.2 — uncited (reference copy)
• limits.0 — uncited (reference copy)
• limits.1 — uncited (reference copy)
• faqs.1.a — uncited (reference copy)