Install Jentic One Beta

Connect the AgentsPodium account API (agent-facing subset) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AgentsPodium account API (agent-facing subset), 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%2Fdefispace.com%2Fdefispace" | 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%2Fdefispace.com%2Fdefispace" | 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 AgentsPodium account API (agent-facing subset) API.

Deploy a new AI agent pod and read, upgrade, pause, resume, rebuild, or delete it

Configure an agent's model key, enabled toolsets and tool servers, messenger channels, and Telegram bot token

Browse the catalog of personas, engines, Hermes toolsets, curated LLM models, and LLM providers

Monitor a pod's liveness, RAM and disk usage, remaining term, and last build status

GET STARTED

Start building with AgentsPodium account API (agent-facing subset) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AgentsPodium account API (agent-facing subset) API for, with concrete tasks.

★ An Agent Provisioning Other Agent Pods

Because the AgentsPodium account API is meant to be driven directly by an agent, an orchestrator connected through Jentic can deploy a new pod from a chosen persona and engine, install its model key, enable the toolsets it needs, and bring it online, all without a human operator. This turns agent provisioning into a programmatic step rather than a dashboard task.

Create a new agent from a persona and engine, install its model key, enable a toolset, and confirm the pod is live

Configuring a Hosted Agent

AgentsPodium exposes each pod's configuration as discrete operations: install or clear the model key, set enabled toolsets and tool servers, choose which messengers the agent listens on, install a Telegram bot token, append owner instructions to the persona, and set the schedule timezone. An agent can reconfigure itself or a peer without redeploying from scratch.

Set the enabled toolsets and tool servers on an agent, then install its Telegram bot token

Lifecycle and Health Management

Owners can manage a pod across its whole lifecycle: check liveness and current RAM and disk usage against the plan, find when the term ends, pause to stop billing resources, resume, rebuild from the last backup, and take an off-pod snapshot. This keeps a fleet of agent pods observable and recoverable from one API.

Check a pod's liveness and usage, and if it is unhealthy, rebuild it from its last backup

Paying for an Agent Plan

AgentsPodium accepts plan payments without a card: open a USDT or USDC crypto deposit order for an agent's plan, or open a Telegram Stars order, then list the orders to confirm settlement. An agent can top up its own hosting term using the payment providers the platform supports.

Open a USDT crypto-order for an agent's plan and then list its crypto orders to confirm the deposit

Key Endpoints

52 endpoints — the agentspodium account api lets an agent create, configure, pay for, and watch hosted ai agent pods directly, without a human operator.

METHOD

PATH

DESCRIPTION

POST

/agents

Create a new agent (deploy a pod)

GET

/agents/{id}

Read one agent's full record

PATCH

/agents/{id}/tools

Set the agent's enabled toolsets and tool servers

POST

/agents/{id}/pause

Pause an agent to stop billing its resources

POST

/agents/{id}/rebuild

Rebuild the pod from its last backup

GET

/agents/{id}/liveness

Check whether the pod is up and answering

POST

/agents/{id}/crypto-order

Open a USDT or USDC deposit order for a plan

GET

/personas

List the public persona catalog

POST

/agents

Create a new agent (deploy a pod)

GET

/agents/{id}

Read one agent's full record

PATCH

/agents/{id}/tools

Set the agent's enabled toolsets and tool servers

POST

/agents/{id}/pause

Pause an agent to stop billing its resources

POST

/agents/{id}/rebuild

Rebuild the pod from its last backup

GET

/agents/{id}/liveness

Check whether the pod is up and answering

POST

/agents/{id}/crypto-order

Open a USDT or USDC deposit order for a plan

GET

/personas

List the public persona catalog

Why Jentic?

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

Setup

Wiring AgentsPodium by hand means handling its bearer auth (an ak_live_ key or a session token from the e-mail verify flow), the persona, engine, tool, and model catalogs, and crypto or Telegram Stars payment orders. Through Jentic you install once, import AgentsPodium from the API Directory, store the key once, and your agent calls it.

Permission scoping

AgentsPodium puts each pod's id in the URL path (/agents/{id}/...), so a rule can pin your agent to one pod and the operations you pick: it can read status, usage, and backups for that pod while deleting it, minting keys, or opening payment orders stay out of reach. You choose the operations it may call, so nothing destructive or billable runs unless you add it.

Credential isolation

Your AgentsPodium 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 'deploy an agent pod' or 'set an agent's toolsets', and Jentic returns the matching AgentsPodium operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using AgentsPodium account API (agent-facing subset) API through Jentic.

Is there an AgentsPodium MCP server?

You don't need an MCP server to give your agent AgentsPodium. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the deploy, configure, lifecycle, and payment operations. The API itself can also set which MCP servers a deployed pod enables, configured through the tools operation.

Can I limit what my agent is allowed to do with AgentsPodium?

Yes. Write a rule that allows the pod read and configuration operations for one agent id but not agent deletion, API-key minting, or crypto and Stars payment orders, so the agent can manage its own pod while your account and billing stay under your control, and every call it makes is logged.

What authentication does the AgentsPodium account API use?

Per its OpenAPI spec, the API uses a bearer token in the Authorization header: either an ak_live_ API key created on the account page, or a session token obtained by exchanging a six-digit e-mail code through the verify operation. Through Jentic the key is stored encrypted by your own Jentic One instance and injected only at call time.

Can I deploy and pause an agent pod with the AgentsPodium account API?

Yes. The create-agent operation deploys a new pod from a persona and engine, and the pause operation stops billing the pod's resources while keeping it; resume brings it back and rebuild restores it from the last backup. You can also read the pod's liveness and usage to decide when to pause or rebuild.

What are the rate limits for the AgentsPodium account API?

The OpenAPI spec does not specify request-rate limits; resource limits are instead tied to each agent's plan, and the usage operation reports current RAM and disk against that plan while the term operation reports when the plan ends. Check hosting.defispace.com for current plan and quota details.

How do I deploy an agent pod with the AgentsPodium account API through Jentic?

Call the create-agent operation with a persona and engine, install the model key and toolsets, then check liveness to confirm the pod is up. In Jentic, search for 'deploy an AI agent pod', store your API key once, and the agent runs the sequence. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Defispace AgentsPodium account API (agent-facing subset)

AI ReadinessFoundational (D+)48/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputebearer52 EndpointsREST

For Agents

Deploy, configure, pay for, and monitor hosted AI agent pods directly from an agent: set models, toolsets, MCP servers, and channels, manage the lifecycle, and connect agents over A2A across 52 endpoints.

Use for: Deploy a new AI agent pod from a persona, Set which toolsets and tool servers my agent has enabled, Pause an agent to stop billing its resources, Check whether my agent's pod is up and answering

Not supported: Does not host general websites, databases, or non-agent workloads, and it does not author the agent's own logic. Use for deploying, configuring, and paying for hosted AI agent pods only.

The AgentsPodium account API lets an agent create, configure, pay for, and watch hosted AI agent pods directly, without a human operator. It deploys a pod from a persona and a chosen engine, installs its model key, enables Hermes toolsets and connected tool servers, sets messenger channels such as Telegram, and manages the full lifecycle with pause, resume, rebuild, backup, and delete. It exposes catalogs of personas, engines, tools, models, and LLM providers, accepts plan payments in USDT, USDC, or Telegram Stars, and connects agents to each other through an A2A peer list and public directory.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

84%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

50%

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.

96%

Example Validity

Percentage of examples that conform to their schemas.

46%

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: FSignals: 4

49%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AgentsPodium account API (agent-facing subset) to your agent

Capabilities

Start building with AgentsPodium account API (agent-facing subset) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Defispace AgentsPodium account API (agent-facing subset)

Jentic AI Readiness Score

AgentsPodium account API (agent-facing subset)

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