Install Jentic One Beta

Connect the Rebilly REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rebilly REST 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%2Frebilly.com%2Frebilly" | 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%2Frebilly.com%2Frebilly" | 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 Rebilly REST API.

Refund a transaction by id with a required amount, and query its status with the gateway

Issue, recalculate, reissue, abandon, or void an invoice, and apply a transaction to it

Change the items on a subscription order, cancel it with a churnTime, or reactivate it later

Preview a customer's or order's upcoming invoices before the next billing run

GET STARTED

Start building with Rebilly REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Rebilly REST API for, with concrete tasks.

★ Billing support agent through Jentic

A support agent handling a billing ticket needs to find the customer's charge and refund it without a human logging into the Rebilly dashboard. Through Jentic the agent searches for 'refund a Rebilly transaction', loads the refund operation with its input schema, and sends the refund amount for the transaction id while the secret key is injected at call time. It can then add a timeline comment on the transaction recording why the refund was made.

Call GET /transactions/{id} to confirm the charge, POST /transactions/{id}/refund with amount 19.99, then POST /transactions/{id}/timeline with a comment noting the support ticket

Invoice lifecycle control

Finance teams correcting invoices need to recalculate after an item change, reissue a corrected copy, or void one sent in error. The Rebilly invoice operations cover each step by invoice id, including adding invoice items, applying an outside payment as a transaction, and reading transaction allocations to see how payments were split. Creating an invoice requires currency, websiteId, and customerId.

Call POST /invoices/{id}/items to add a credit line, POST /invoices/{id}/recalculate, then POST /invoices/{id}/reissue for the corrected invoice

Subscription change and cancellation

A subscription business lets customers upgrade, downgrade, or cancel. Rebilly changes an order's items through its change-items operation, records cancellations through subscription cancellations with a required subscriptionId and churnTime, and restores service through subscription reactivations. Upcoming invoice previews show the customer what the next bill will be before the change takes effect.

Call GET /subscriptions/{id}/upcoming-invoices to preview the next bill, then POST /subscription-cancellations with the subscriptionId and a churnTime at the period end

KYC and AML screening

Merchants in regulated verticals verify customers before accepting payments. Rebilly stores KYC documents and requests, and exposes acceptance, rejection, review, and document-match operations so a compliance workflow can record each decision. The AML search checks a name, date of birth, and country against PEP, sanctions, and adverse media lists.

Call GET /aml with firstName 'Jane', lastName 'Doe', dob '1980-04-12', and country 'GB', then POST /kyc-documents/{id}/review for the customer's uploaded document

Key Endpoints

184 endpoints — the rebilly rest api runs subscription billing and payment processing for online businesses, from customer records and payment instruments to orders, invoices, and transactions.

METHOD

PATH

DESCRIPTION

POST

/transactions/{id}/refund

Refund a transaction

GET

/transactions

List transactions

POST

/invoices/{id}/issue

Issue an invoice

POST

/invoices/{id}/void

Void an invoice

POST

/subscriptions

Create a subscription order

POST

/subscription-cancellations

Cancel a subscription order

GET

/customers/{id}

Retrieve a customer

GET

/aml

Search PEP, sanctions, and adverse media lists

POST

/transactions/{id}/refund

Refund a transaction

GET

/transactions

List transactions

POST

/invoices/{id}/issue

Issue an invoice

POST

/invoices/{id}/void

Void an invoice

POST

/subscriptions

Create a subscription order

POST

/subscription-cancellations

Cancel a subscription order

GET

/customers/{id}

Retrieve a customer

GET

/aml

Search PEP, sanctions, and adverse media lists

Why Jentic?

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

Setup

Wiring Rebilly by hand means choosing between a secret key in the REB-APIKEY header and a JWT bearer token, switching between the sandbox and live hosts, and knowing which payment token calls need a publishable key instead. Through Jentic you install once, import Rebilly from the API Directory, store the key once, and your agent calls it.

Permission scoping

Rebilly puts the record id in the URL path for transactions, invoices, orders, and customers (/transactions/{id}/refund, /invoices/{id}/void), so a rule can limit your agent to one record and the operations you pick. You choose the operations it may call, so destructive ones like voiding an invoice or merging and deleting a customer are not included unless you add them.

Credential isolation

Your Rebilly secret key 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 'refund a Rebilly transaction' or 'void an invoice', and Jentic returns the matching Rebilly operation with its input schema, including required body fields like amount or churnTime.

FAQs

Specific to using Rebilly REST API through Jentic.

What authentication does the Rebilly REST API use?

Per its OpenAPI spec, most operations accept either a secret API key in the REB-APIKEY header or a JWT sent as an HTTP bearer token. A publishable API key, sent in the Authorization header, is accepted on the payment token operations, and GET /tokens/{token} and digital wallet validation use it alone. Through Jentic your key is stored by your own instance and attached at call time.

Can I refund a payment with the Rebilly REST API?

Yes. POST /transactions/{id}/refund refunds a transaction and requires an amount in the body, so partial refunds are expressed by sending less than the original amount. GET /transactions/{id} returns the original transaction first, and POST /transactions/{id}/query asks the gateway for its latest status.

What are the rate limits for the Rebilly REST API?

The OpenAPI spec does not specify rate limits. Check the Rebilly developer documentation at https://docs.rebilly.com/ for current limits.

Is there a Rebilly MCP server?

You don't need an MCP server to give your agent Rebilly. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the billing operations it needs on demand without loading extra tool definitions into its context.

How do I cancel a subscription order through Jentic?

Search Jentic for 'cancel a Rebilly subscription', load the POST /subscription-cancellations operation, and run it with the subscriptionId and a churnTime. Call GET /subscriptions/{id}/upcoming-invoices first if the customer wants to see their final bill. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I use the Rebilly sandbox?

Yes. The spec lists two servers: api-sandbox.rebilly.com for the sandbox and api.rebilly.com for live traffic. Point the agent at the sandbox host with a sandbox key while you test refunds and invoice changes.

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

Yes. For example, allow only GET /transactions/{id} and POST /transactions/{id}/refund for the transaction id named in a ticket, and the agent can check and refund that one charge but cannot void invoices, cancel orders, or touch KYC records, with every call logged.

Rebilly REST API

Browse all Rebilly APIs

AI ReadinessFoundational (C)57/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsBilling SubscriptionsapiKey, bearer184 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Look up Rebilly customers, orders, invoices, and transactions, refund a transaction, issue or void an invoice, cancel or reactivate a subscription order, and review KYC documents.

Use for: Refund part of a Rebilly transaction, Void an invoice that was issued in error, Retrieve the upcoming invoice for a subscription order, Cancel a customer's subscription at the end of the period

Not supported: Does not file taxes, run payroll, or keep a general ledger. Use for Rebilly subscription billing, invoicing, payment transactions, and KYC records only.

The Rebilly REST API runs subscription billing and payment processing for online businesses, from customer records and payment instruments to orders, invoices, and transactions. It issues, recalculates, reissues, and voids invoices, applies transactions to them, and refunds or queries individual transactions. Subscription orders can have their items changed, be cancelled or reactivated, and generate interim or upcoming invoices. The same surface covers coupons and redemptions, disputes, blocklists, KYC documents and requests, and screening against PEP, sanctions, and adverse media lists.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

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.

96%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: C+Signals: 4

71%

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.

64%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: DSignals: 1

46%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C+Signals: 1

58%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Rebilly REST API to your agent

Capabilities

Start building with Rebilly REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Rebilly REST API

Jentic AI Readiness Score

Rebilly REST API

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