Paraio Para API

Name: Para API
Brand: Para API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage Registryhttp4 EndpointsREST

For Agents

Manage backend objects with CRUD operations across 4 endpoints using flexible object types.

Install Jentic One Beta

Connect the Para API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Para 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%2Fparaio.org%2Fmain" | 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%2Fparaio.org%2Fmain" | 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 Para API.

Create objects of any custom type

List objects by type with sorting, pagination, and descending order

Read objects by ID and type

Update objects with partial modifications

GET STARTED

Start building with Para API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Para API for, with concrete tasks.

★ Type-Agnostic Object Storage

Store and manage objects of any custom type without predefined schemas. POST /{type} creates objects, GET /{type} lists them with sorting and pagination (sort, desc, limit, page parameters), and the type parameter supports any custom schema (users, posts, products, etc).

POST /{type} to create, GET /{type}?sort=created&desc=true&limit=50 to list with sorting

Object CRUD Operations

Perform complete CRUD operations on backend objects. POST /{type} creates, GET /{type}/{id} reads, PATCH /{type}/{id} updates, and DELETE /{type}/{id} removes objects. Each operation works with any custom type, providing flexible backend management.

POST /{type} to create, GET /{type}/{id} to read, PATCH to update, DELETE to remove

Paginated Object Listing

Retrieve object collections with pagination, sorting, and filtering. GET /{type} returns items array and totalHits with support for sort (field name), desc (boolean), limit (max results), and page (page number) parameters. Essential for building paginated interfaces.

GET /{type}?sort=timestamp&desc=true&limit=20&page=1 for paginated, sorted results

Agent-Driven Backend Management via Jentic

An AI agent managing backend infrastructure can create, read, update, and delete objects through Jentic without exposing authentication tokens in agent context. Jentic resolves intents like 'list user objects' to the right Para endpoint with proper type parameters.

Search Jentic for 'list backend objects', load the GET /{type} schema, and execute

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for para api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/{type}

Create a new object

GET

/{type}

List objects of a type

GET

/{type}/{id}

Read an object by ID

PATCH

/{type}/{id}

Update an object

POST

/{type}

Create a new object

GET

/{type}

List objects of a type

GET

/{type}/{id}

Read an object by ID

PATCH

/{type}/{id}

Update an object

Why Jentic?

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

Setup

Wiring this Para deployment by hand means resolving your own host, computing AWS Signature V4 or carrying a JWT bearer token, and shaping the generic /{type} object routes yourself. Through Jentic you install once, import Para from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Para puts the object type and id in the URL path (/{type}/{id}), so a rule can pin your agent to one object type: it can create, read, and list those objects. You choose the operations it may call, so writes to other types are not included unless you add them.

Credential isolation

Your Para bearer token or signing credential 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 object' or 'list objects of a type', and Jentic returns the matching Para operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Para API through Jentic.

Why is there no official OpenAPI spec for Para API?

Para is open-source but does not publish a complete OpenAPI specification for their REST API. Jentic generates and maintains this spec so that AI agents and developers can call Para API via structured tooling. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Para API use?

Para API uses HTTP bearer token authentication. Through Jentic, tokens are stored in the encrypted vault and injected at execution time so they never enter the agent's prompt context.

Can I define custom object types?

Yes. The {type} path parameter accepts any custom object type name (users, posts, orders, etc). Para stores objects flexibly without requiring predefined schemas, allowing you to create your own data models.

How does sorting work?

GET /{type} accepts sort (field name) and desc (boolean for descending order) query parameters. For example, ?sort=created&desc=true sorts by created field in descending order.

What is the difference between paraio.com and paraio.org?

Both represent the same Para backend framework. paraio.com typically refers to the hosted service while paraio.org is the open-source project site. The API endpoints work identically regardless of deployment.

Is Para suitable for production use?

Yes. Para is a production-ready, open-source backend framework used by many applications. It can be self-hosted or used as a hosted service, providing flexibility for different deployment requirements.

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

Yes. Because you run Jentic One yourself, your own rules decide which Para operations and credentials the agent may use, and Para puts the object type and id in the URL path (/{type}/{id}), so you can pin the agent to a single object type. You might allow it only to create objects (POST /{type}), read one by id (GET /{type}/{id}), and list a type (GET /{type}), while withholding PATCH /{type}/{id} updates and DELETE calls or access to any other type. Nothing outside the operations you grant is available to the agent.

Paraio Para API

Connect the Para API to your agent

Capabilities

Start building with Para API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs