Withpersona API Reference

Name: API Reference API
Brand: API Reference
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbearer237 EndpointsREST

For Agents

Programmatically create an account, list all accounts. Covers 237 operations with bearer authentication.

Install Jentic One Beta

Connect the API Reference to your agent

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

Create an Account

List all Accounts

Retrieve an Account

Update an Account

GET STARTED

Start building with API Reference API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use API Reference API for, with concrete tasks.

★ Developer Tools Operations

Use the API Reference to perform developer tools operations programmatically. The API provides 237 endpoints covering core functionality including create an account, list all accounts, retrieve an account.

Call POST /accounts to create an account

Automated subpackage_aamvaVerifications Management

Automate subpackage_aamvaverifications operations by combining multiple API Reference endpoints. Agents can list all accounts and then retrieve an account in a single workflow.

Call GET /accounts to list all accounts, then verify the result

AI Agent Integration via Jentic

AI agents discover and call API Reference 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.

Search Jentic for 'create an account', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

237 endpoints — api reference provides programmatic access to developer tools functionality.

METHOD

PATH

DESCRIPTION

POST

/accounts

Create an Account

GET

/accounts

List all Accounts

GET

/accounts/{account-id}

Retrieve an Account

PATCH

/accounts/{account-id}

Update an Account

DELETE

/accounts/{account-id}

Redact an Account

POST

/accounts/{account-id}/add-tag

Add tag to an Account

POST

/accounts/{account-id}/consolidate

Consolidate Accounts

GET

/accounts/{account-id}/relations

Get all relations for an Account

POST

/accounts

Create an Account

GET

/accounts

List all Accounts

GET

/accounts/{account-id}

Retrieve an Account

PATCH

/accounts/{account-id}

Update an Account

DELETE

/accounts/{account-id}

Redact an Account

POST

Why Jentic?

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

Setup

Wiring the Persona API by hand means learning its bearer auth, targeting api.withpersona.com, and composing account, tag, and relation calls yourself. Through Jentic you install once, import the Persona API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Persona puts the account id in the URL path (/accounts/{account-id}), so a rule can pin your agent to reading one account and its relations. You choose the operations it may call, so destructive ones like deleting an account are not included unless you add them.

Credential isolation

Your Persona 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.

Intent-based discovery

Agents search Jentic by intent such as 'create an account' or 'add a tag to an account', and Jentic returns the matching Persona operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using API Reference API through Jentic.

What authentication does the API Reference use?

The API Reference 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 create an account with the API Reference?

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

What are the rate limits for the API Reference?

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 an account through Jentic?

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

How many endpoints does the API Reference have?

The API Reference exposes 237 endpoints covering subpackage_aamvaverifications, subpackage_accounts, subpackage_apikeys operations.

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

Yes. Jentic One is self-hosted by you, and your own rules decide which Persona operations and credentials your agent may use. Because Persona puts the account id in the URL path (/accounts/{account-id}), you can pin the agent to reading a single account and its relations while excluding actions like creating, updating, or tagging accounts. Destructive operations such as redacting an account are only available if you explicitly grant them, and the stored Persona token is injected at execution time rather than exposed to the agent.