canonical: https://jentic.com/apis/revaluate.com/revaluate

# Revaluate API

The Revaluate API provides access to contact scoring data, billing information, user management, and webhook subscriptions. Revaluate helps identify contacts likely to move by analyzing behavioral signals. The API exposes 18 endpoints secured with bearer authentication.

## For AI agents

Programmatically check token validity, get billing details. Covers 18 operations with bearer authentication.

## Scope

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

## Capabilities

- Check token validity
- Get billing details
- Create a contact
- List contacts
- Update a contact
- Delete a contact

## Use cases

### Payments Operations

Use the Revaluate API to perform payments operations programmatically. The API provides 18 endpoints covering core functionality including check token validity, get billing details, create a contact.

Example prompt: Call GET `/users/check_token` to check token validity

### Automated Authentication Management

Automate authentication operations by combining multiple Revaluate API endpoints. Agents can get billing details and then create a contact in a single workflow.

Example prompt: Call GET /billing to get billing details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Revaluate 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 bearer tokens manually.

Example prompt: Search Jentic for 'check token validity', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/users/check_token` | Check token validity |
| GET | `/billing` | Get billing details |
| POST | `/contacts` | Create a contact |
| GET | `/contacts` | List contacts |
| GET | `/contacts/{id}` | Get a contact |
| PUT | `/contacts/{id}` | Update a contact |
| DELETE | `/contacts/{id}` | Delete a contact |
| POST | `/contacts/show_by_email` | Get contact by email |

## Key resources

- **Authentication** — Token validation
- **Billing** — Account billing details
- **Contacts** — Contact management
- **Users** — User management (partner accounts)
- **SSO** — Single sign-on token generation

## Why Jentic

- **Setup:** Wiring the Revaluate API by hand means learning its bearer token auth, targeting the api.revaluate.com/v1 host, and managing contact and billing calls yourself. Through Jentic you install once, import Revaluate API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Revaluate API puts the contact id in the URL path (`/contacts/{id}`), so a rule can pin your agent to one contact: it can read and update that contact and nothing else. You choose the operations it may call, so destructive ones like contact deletion are not included unless you add them.
- **Credential handling:** Your Revaluate API 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a contact' or 'find a contact by email', and Jentic returns the matching Revaluate 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 Revaluate API use?

The Revaluate API uses a Bearer token in the Authorization header. 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 check token validity with the Revaluate API?

Yes. Use the GET `/users/check_token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Revaluate 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 check token validity through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check token validity'. Jentic returns the matching Revaluate API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Revaluate API have?

The Revaluate API exposes 18 endpoints covering authentication, billing, contacts operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Revaluate API operations and credentials the agent may use. Since the API puts the contact id in the URL path (`/contacts/{id}`), you can pin the agent to a single contact so it only reads and updates that one record and touches nothing else. You also choose the operation set, so destructive calls such as DELETE `/contacts/{id}` stay out of reach unless you explicitly grant them.