Raia2 AI Agent API

Name: AI Agent API
Brand: AI Agent API
Availability: InStock

✓ Official Vendor SpecCommunicationsSms MessagingapiKey38 EndpointsREST

For Agents

Programmatically create a conversation user, find user by contact information. Covers 38 operations with apiKey authentication.

Install Jentic One Beta

Connect the AI Agent API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AI Agent 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 AI Agent API.

Create a conversation user

Find user by contact information

Get conversation user by ID

Delete conversation user by ID

GET STARTED

Start building with AI Agent API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AI Agent API for, with concrete tasks.

★ Communications Operations

Use the AI Agent API to perform communications operations programmatically. The API provides 38 endpoints covering core functionality including create a conversation user, find user by contact information, get conversation user by id.

Call POST /external/users to create a conversation user

Automated External Management

Automate external operations by combining multiple AI Agent API endpoints. Agents can find user by contact information and then get conversation user by id in a single workflow.

Call GET /external/users/search to find user by contact information, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'create a conversation user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

38 endpoints — api for creating users, conversations, and sending messages.

METHOD

PATH

DESCRIPTION

POST

/external/users

Create a conversation user

GET

/external/users/search

Find user by contact information

GET

/external/users/{id}

Get conversation user by ID

DELETE

/external/users/{id}

Delete conversation user by ID

POST

/external/conversations

Create a new conversation

GET

/external/conversations

Get conversations

DELETE

/external/conversations

Delete all user conversations in current agent

GET

/external/conversations/states

Get conversation states

POST

/external/users

Create a conversation user

GET

/external/users/search

Find user by contact information

GET

/external/users/{id}

Get conversation user by ID

DELETE

/external/users/{id}

Delete conversation user by ID

POST

/external/conversations

Create a new conversation

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your raia 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 'create a raia user' or 'start a conversation', and Jentic returns the matching raia operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using AI Agent API through Jentic.

What authentication does the AI Agent API use?

The AI Agent API uses an API key passed in the `Agent-Secret-Key` 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 a conversation user with the AI Agent API?

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

What are the rate limits for the AI Agent 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 conversation user through Jentic?

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

How many endpoints does the AI Agent API have?

The AI Agent API exposes 38 endpoints covering external operations.

Can I limit what my agent is allowed to do with the raia AI Agent API?

Yes. Because you run Jentic One yourself, your own rules decide which raia operations and credentials the agent may use. Since raia puts the user id in the URL path (/external/users/{id}), a rule can pin the agent to a single user so it reads only that user and nothing else. You also pick the exact operations it can call, so destructive ones like deleting a user (DELETE /external/users/{id}) or clearing conversations (DELETE /external/conversations) stay out of reach unless you add them.

Raia2 AI Agent API

Connect the AI Agent API to your agent

Capabilities

Start building with AI Agent API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs