Metorial API

Name: Metorial API
Brand: Metorial API
Availability: InStock

✓ Official Vendor SpecAI/MLLanguage Modelsbearer21 EndpointsREST

For Agents

Manage AI provider integrations, identities, and sessions so agents can talk to upstream model providers under a single, governed control plane.

Install Jentic One Beta

Connect the Metorial API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Metorial 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 Metorial API.

Create, update, and delete identities that map agents or human users to provider credentials

Open sessions that bind an identity to a provider configuration for a working agent run

GET STARTED

Start building with Metorial API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Metorial API for, with concrete tasks.

★ Centralised AI Provider Credential Management

Engineering teams running multiple agents across providers like OpenAI, Anthropic, and self-hosted models avoid scattering API keys by registering each provider once in Metorial and creating per-agent identities that reference the central configuration. The /provider-configs and /identities endpoints let platform owners rotate credentials in one place while agents continue to call through their stable identity.

Create a provider configuration for OpenAI with the production credential, then create an identity scoped to it and verify it via GET /provider-configs/{id}.

Per-Agent Session Isolation

When an autonomous agent runs many parallel tasks, each task can be scoped to its own Metorial session so quotas, audit logs, and credential exposure stay isolated. POST /sessions binds an identity to a provider configuration for the lifetime of a job, and PATCH /sessions/{id} lets the orchestrator update metadata as the agent progresses.

Create a session for identity 'agent-42' tied to provider config 'anthropic-prod', then update the session description with the running task ID.

Multi-Tenant AI Platform Onboarding

Platforms that resell AI capabilities to many customers can use Metorial publishers and provider deployments to expose curated provider catalogues per tenant. The publishers and provider-deployments endpoints describe what is available, while identities map customers to the right credential tier without leaking secrets between tenants.

List all publishers, then for the selected publisher list the provider deployments and create an identity tied to the chosen deployment.

Agent Provisioning Through Jentic

An autonomous agent that needs an AI provider can call Metorial through Jentic to provision an identity and open a session on demand. The agent searches for the operation by intent, loads the schema for POST /identities or POST /sessions, and executes with arguments derived from the runtime context — without ever holding the bearer token directly.

Search Jentic for 'create an AI agent identity', load POST /identities, then POST /sessions for the new identity, and return the session ID.

Key Endpoints

21 endpoints — metorial is a control plane for ai integrations that lets teams register providers, attach identities and credentials, and orchestrate sessions that downstream agents and applications can use.

METHOD

PATH

DESCRIPTION

POST

/identities

Create a new identity for an agent or user

POST

/sessions

Open a session binding an identity to a provider configuration

GET

/sessions/{id}

Retrieve session details

POST

/provider-configs

Create a provider configuration

PATCH

/provider-configs/{id}

Update an existing provider configuration

GET

/providers

List available AI providers

POST

/identities

Create a new identity for an agent or user

POST

/sessions

Open a session binding an identity to a provider configuration

GET

/sessions/{id}

Retrieve session details

POST

/provider-configs

Create a provider configuration

PATCH

/provider-configs/{id}

Update an existing provider configuration

Why Jentic?

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

Credential isolation

The Metorial bearer token is stored encrypted in the Jentic vault. Agents receive scoped access to operations and Jentic sets the Authorization header at execution time, so the raw token never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'create an AI agent identity' or 'open a Metorial session' and Jentic returns the matching Metorial operation with its input schema, removing the need to read the API reference.

Time to first call

Direct Metorial integration: 1-2 days for token handling, identity lifecycle, and session bookkeeping. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Metorial API through Jentic.

What authentication does the Metorial API use?

Metorial uses HTTP bearer authentication — every request needs an Authorization header with a token issued from your Metorial instance. Through Jentic the token lives in the encrypted vault and is injected at call time so agents never handle it directly.

Can I create multiple identities under one provider configuration?

Yes. POST /identities creates an identity, and you can then attach it to an existing provider configuration via a session. This is the recommended pattern for fanning out many agents while keeping a single rotated credential.

What are the rate limits for the Metorial API?

Metorial does not document fixed rate limits in this OpenAPI spec — limits are tenant-specific and set by your Metorial deployment. Inspect response headers and back off on 429 responses; for high-volume orchestrators contact Metorial support to raise the cap.

How do I open a session for an agent through Jentic?

Search Jentic for 'create a Metorial session', load POST /sessions, and execute with the identity ID and provider configuration ID. Jentic handles the bearer token from your stored Metorial credential.

Does Metorial actually call upstream LLM providers for me?

Metorial is the control plane for identities, sessions, and provider configurations — actual model invocations happen at the provider you configure, with Metorial managing the credential and session boundary around each call.

Can I update a provider configuration without breaking active sessions?

PATCH /provider-configs/{id} updates fields in place. Active sessions continue to reference the same configuration; if you rotate the underlying credential, the new value takes effect for subsequent calls without re-creating sessions.

Metorial API

Connect the Metorial API to your agent

Capabilities

Start building with Metorial API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs