canonical: https://jentic.com/apis/rev.io/rev

# Rev.io API

Billing and subscription management API. The API exposes 23 endpoints.

## For AI agents

Programmatically create a new address, search for one or more addresses. Covers 23 operations.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Create a new address
- Search for one or more addresses
- Retrieve single address by ID
- Update/replace existing address
- Partial update of address
- Delete address

## Use cases

### Payments Operations

Use the Rev.io API to perform payments operations programmatically. The API provides 23 endpoints covering core functionality including create a new address, search for one or more addresses, retrieve single address by id.

Example prompt: Call POST /Addresses to create a new address

### Automated addresses Management

Automate addresses operations by combining multiple Rev.io API endpoints. Agents can search for one or more addresses and then retrieve single address by id in a single workflow.

Example prompt: Call GET /Addresses to search for one or more addresses, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rev.io API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'create a new address', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/Addresses` | Create a new address |
| GET | `/Addresses` | Search for one or more addresses |
| GET | `/Addresses/{id}` | Retrieve single address by ID |
| PUT | `/Addresses/{id}` | Update/replace existing address |
| PATCH | `/Addresses/{id}` | Partial update of address |
| DELETE | `/Addresses/{id}` | Delete address |
| POST | `/Customers` | Create a new customer |
| GET | `/Customers` | Search for customers |

## Key resources

- **addresses** — Address management
- **customers** — Customer management
- **billing** — Billing operations
- **payments** — Payment processing
- **services** — Service management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 49 / 100
  - Developer Experience & Jentic Compatibility: 55 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/rev.io/rev/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Rev.io API by hand means targeting the restapi.rev.io/v1 host and managing address and customer record calls yourself. Through Jentic you install once, import Rev.io API from the API Directory, and your agent calls it without extra wiring.
- **Permission scoping:** Rev.io API puts the record id in the URL path (`/Addresses/{id}`, `/Customers/{id}`), so a rule can pin your agent to one address or customer: it can read and update that record and nothing else. You choose the operations it may call, so destructive ones like record deletion are not included unless you add them.
- **Credential handling:** Any Rev.io API configuration your own Jentic One instance holds is stored once, encrypted, and injected at execution time. Nothing sensitive enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a new address' or 'list customers', and Jentic returns the matching Rev.io API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Rev.io API use?

The Rev.io API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a new address with the Rev.io API?

Yes. Use the POST /Addresses endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Rev.io API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a new address through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new address'. Jentic returns the matching Rev.io API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Rev.io API have?

The Rev.io API exposes 23 endpoints covering addresses, customers, billing operations.

### Can I limit what my agent is allowed to do with the Rev.io API?

Yes. Because you run Jentic One yourself, your own rules decide which Rev.io API operations and credentials the agent may use. Since the API puts the record id in the URL path (`/Addresses/{id}`, `/Customers/{id}`), a rule can pin the agent to a single address or customer so it can read and update that record and nothing else. You also choose which operations are in scope, so a destructive call like DELETE `/Addresses/{id}` is only available if you add it.
