Install Jentic One Beta

Connect the plori REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the plori REST 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%2Fplori.ai%2Fplori" | 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%2Fplori.ai%2Fplori" | 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 plori REST API.

Create a cloud agent by name with a model and config, or get the existing one with if_exists set to return

Submit a run to an agent with a message and caps such as max_turn_tokens, max_advisor_spend_micro_usd, or max_turn_seconds, replaying safely with an Idempotency-Key

Poll a run's status, list an agent's runs, and cancel an in-flight run

Schedule a deferred one-shot run with a prompt and fire_at or delay_seconds, then confirm or cancel it

GET STARTED

Start building with plori REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use plori REST API for, with concrete tasks.

★ Agent-to-Agent Delegation via Jentic

A local coding or ops agent hands longer work to a hosted plori agent instead of running it in its own session. Through Jentic it calls createAgent with if_exists set to return so one agent is reused, submits a run with a message and a max_turn_seconds cap, polls getAgentRun until the run finishes, and reads any result files with readAgentFile.

Create or get the agent named 'research-bot', submit a run asking it to summarise this week's changelog with max_turn_seconds 600 and an Idempotency-Key, then poll getAgentRun until it completes

GitHub Actions Without Stored Secrets

Repository owners trigger a plori agent from a workflow without saving an API key in GitHub. The workflow sends its OIDC JWT, minted for audience plori.ai, to the exchange operation and receives a short-lived plori_ghr_ capability that can submit exactly one run to that repository's agent and poll only that run's event stream.

In a GitHub Actions job, exchange the OIDC token at /v1/github/oidc/exchange, submit one run to the repository agent with the returned capability, and poll /v1/github/runs/{runID} for its events

Deferred and Scheduled Agent Runs

Teams that want an agent to act later, such as a morning report or a follow-up check, create a schedule with a prompt and either fire_at or delay_seconds. A schedule created directly with the owner's plori_sk_ key starts pending, while one created with an OAuth access token waits for the owner to confirm it, so a schedule booked through an OAuth client does not fire until the owner approves it.

Create a schedule on agent agt_123 with prompt 'Post the weekly metrics summary' and delay_seconds 86400, then list schedules to check whether it is pending or awaiting_confirmation

Key Endpoints

20 endpoints — the plori rest api creates and runs hosted cloud agents, schedules deferred runs, and lets github actions trigger a repository's agent without a stored key.

METHOD

PATH

DESCRIPTION

POST

/v1/agents

Create or get-or-create an agent

POST

/v1/agents/{agentID}/runs

Submit a run to an agent

GET

/v1/agents/{agentID}/runs/{runID}

Get one run's status

POST

/v1/agents/{agentID}/runs/{runID}/cancel

Cancel an in-flight run

POST

/v1/agents/{agentID}/schedules

Schedule a deferred one-shot run

GET

/v1/agents/{agentID}/files/read

Read a window of a file on the agent's disk

POST

/v1/github/oidc/exchange

Exchange a GitHub OIDC token for one run

GET

/v1/pricing/models

Read the public model rate card

POST

/v1/agents

Create or get-or-create an agent

POST

/v1/agents/{agentID}/runs

Submit a run to an agent

GET

/v1/agents/{agentID}/runs/{runID}

Get one run's status

POST

/v1/agents/{agentID}/runs/{runID}/cancel

Cancel an in-flight run

POST

/v1/agents/{agentID}/schedules

Schedule a deferred one-shot run

GET

/v1/agents/{agentID}/files/read

Read a window of a file on the agent's disk

POST

/v1/github/oidc/exchange

Exchange a GitHub OIDC token for one run

GET

/v1/pricing/models

Read the public model rate card

Why Jentic?

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

Setup

Wiring plori by hand means minting a plori_sk_ key or an OAuth 2.1 token, sending Idempotency-Key headers on billable runs, polling submit-only runs, and handling the owner-confirmation step on schedules. Through Jentic you install once, import plori from the API Directory, store the key once, and your agent calls it.

Permission scoping

plori puts the agent id in the URL path (/v1/agents/{agentID}/...), so a rule can pin your agent to one plori agent and the operations you pick, such as submitting runs and reading their status. You choose the operations it may call, so agent creation, schedule creation, and file downloads are not included unless you add them.

Credential isolation

Your plori API 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 'send a message to a cloud agent' or 'schedule an agent run', and Jentic returns the matching plori operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using plori REST API through Jentic.

What authentication does the plori REST API use?

The plori REST API declares two bearer schemes in its OpenAPI spec. Account operations use bearerAuth, which takes a plori_sk_ API key from the dashboard or plori login, or an OAuth 2.1 access token. GitHub-triggered runs use githubRunAuth, a short-lived plori_ghr_ capability returned only by the GitHub OIDC exchange, which can submit one run to one repository agent and poll that run. The OIDC exchange and the two pricing operations are open. Through Jentic the API key is stored encrypted on your own instance and injected at call time.

Is there a plori MCP server?

You don't need an MCP server to give your agent plori. Jentic connects it directly from the API Directory: import plori, store your API key once, and your agent can create agents and submit runs straight away. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

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

Yes. Write a rule that allows only invokeAgent and getAgentRun under /v1/agents/{agentID} for one agent id, so your agent can send that agent messages and poll the results but cannot create agents, schedule future runs, or download files, and the calls it makes are logged.

How do I get the output of a plori run?

Submitting a run returns 202 immediately and does not block. Poll getAgentRun at /v1/agents/{agentID}/runs/{runID} for status; the spec notes that the reply text itself is read over the session WebSocket or the plori CLI. Files the agent writes can be read with readAgentFile or downloaded with downloadAgentFile.

What are the rate limits for the plori REST API?

The plori OpenAPI spec does not publish request rate limits. Runs are billed against your credit balance, which getCredits reports, and the public rate cards at /v1/pricing/models and /v1/pricing/tools list prices. See https://plori.ai for current limits.

How do I submit a run to a plori agent through Jentic?

Search Jentic for an intent like 'send a message to a cloud agent', import plori, and store your plori_sk_ key once. Your agent then calls createAgent with if_exists set to return, submits a run with invokeAgent and an Idempotency-Key, and polls getAgentRun. To run it on your own infrastructure, install Jentic One from its GitHub repo.

plori REST API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer20 EndpointsREST

For Agents

Create a hosted plori agent, send it messages as billable runs, poll or cancel those runs, schedule deferred runs, and read files from the agent's disk. Also exchanges a GitHub Actions OIDC token for a single-run capability and reads public pricing.

Use for: I need to create a long-lived plori agent called repo-maintainer, Send my plori agent a message to review the latest commit, Check whether my plori run has finished, Cancel the run that is still in flight

Not supported: Does not handle direct model completions, code sandbox execution, or reading run replies over HTTP. Use for creating, running, scheduling, and inspecting hosted plori agents only.

The plori REST API creates and runs hosted cloud agents, schedules deferred runs, and lets GitHub Actions trigger a repository's agent without a stored key. You create an agent by name with an optional model and config, using get-or-create so a long-lived agent is reused, then submit runs with a message and limits such as max_turn_tokens or max_turn_seconds; a run is submit-only and returns 202, and you poll its status or cancel it. Files on an agent's disk can be read in windows or downloaded. Schedules fire a one-shot prompt at a set time, with owner confirmation required for schedules created with an OAuth token, and public rate cards list model and tool pricing.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

38%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the plori REST API to your agent

Capabilities

Start building with plori REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

plori REST API

Jentic AI Readiness Score

plori REST API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness