Install Jentic One Beta

Connect the OpenMayhem API to your agent

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

Generate chat completions and embeddings through OpenAI-compatible endpoints, with optional server-sent event streaming

Cap what a single request may spend with the X-OpenMayhem-Max-Cost-Usd header, or price it first with POST /estimates

Queue image, video, text-to-speech, transcription, audio, and music generation jobs, then poll GET /jobs/{id} for status, cost, and artifacts

Run ComfyUI workflow graphs with input files as jobs

GET STARTED

Start building with OpenMayhem API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use OpenMayhem API for, with concrete tasks.

★ Cost-capped model calls from your agent

An AI agent working through Jentic sends POST /chat/completions with a model and messages, and sets X-OpenMayhem-Max-Cost-Usd so the request cannot spend past a limit. Each response carries an openmayhem.request_id, and GET /requests/{id} returns the settled usage, cost, and provider-signed receipt so the agent or its operator can audit what was charged. Your own Jentic One instance injects the sk-om-v1- key at call time.

Call POST /chat/completions with a model, two messages, max_tokens 500, and X-OpenMayhem-Max-Cost-Usd 0.05, then fetch GET /requests/{id} with the returned request id and report the settled cost

Choosing a model by price and capability

Before committing to a model, GET /models filters the public model list by modality, minimum context tokens, maximum input and output price per million tokens, structured output, and tool support. GET /models/by-id/stats and GET /models/by-id/availability add throughput, latency, and provider availability, so an agent can pick the cheapest model that meets its context and reliability needs.

Call GET /models with min_context_tokens 128000 and max_input_price_per_million_usd 1, then GET /models/by-id/stats for the top three and pick the fastest

Media generation jobs

Image, video, speech, transcription, music, and audio generation run as jobs rather than synchronous calls. POST /images/generations or POST /videos returns a job, GET /jobs/{id} reports its status, cost, and artifacts, GET /artifacts/{id} downloads a result, and POST /artifacts/{id}/link creates a short-lived link to share it. DELETE /jobs/{id} cancels a job that is still running.

POST /images/generations with a model, prompt, and size, poll GET /jobs/{id} until it completes, then create a link with POST /artifacts/{id}/link

Credit and spend monitoring

GET /balance returns posted, reserved, and available USD credit, and POST /estimates validates a request against live pricing and key limits without placing a credit hold or charging, so an agent can check that a large batch fits the remaining credit before it starts.

Call GET /balance, then POST /estimates with endpoint /chat/completions and the planned request body, and proceed only if the estimate is below available credit

Key Endpoints

30 endpoints — the openmayhem api sells pay-per-use ai inference routed across a decentralised network of model providers, with openai-compatible chat completions, completions, responses, and embeddings endpoints.

METHOD

PATH

DESCRIPTION

POST

/chat/completions

Chat completion

POST

/embeddings

Embedding vectors

POST

/estimates

Estimate a billable request

GET

/requests/{id}

Settled usage, cost, and receipt

POST

/images/generations

Image generation job

GET

/jobs/{id}

Poll job status, cost, and artifacts

GET

/balance

Read account credit

GET

/models

List models with filters

POST

/chat/completions

Chat completion

POST

/embeddings

Embedding vectors

POST

/estimates

Estimate a billable request

GET

/requests/{id}

Settled usage, cost, and receipt

POST

/images/generations

Image generation job

GET

/jobs/{id}

Poll job status, cost, and artifacts

GET

/balance

Read account credit

GET

/models

List models with filters

Why Jentic?

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

Setup

Wiring OpenMayhem by hand means issuing a scoped sk-om-v1- key, sending it as a bearer token, polling media jobs to completion, and handling Retry-After on 429s. Through Jentic you install once, import OpenMayhem from the API Directory, store the key once, and your agent calls it.

Permission scoping

Rules bound OpenMayhem by operation: the model and prompt travel in the request body, so a rule decides which endpoint families your agent may call, such as chat but not video, not which model it picks. You choose the operations it may call, so DELETE /jobs/{id} and the costlier media jobs are not included unless you add them.

Credential isolation

Your OpenMayhem 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 'generate a chat completion' or 'check my credit balance', and Jentic returns the matching OpenMayhem operation with its input schema, including model, messages, and the optional cost-cap headers, so the agent calls it directly.

FAQs

Specific to using OpenMayhem API through Jentic.

What authentication does the OpenMayhem API use?

The OpenMayhem API uses a bearer token per its OpenAPI spec, with a key from the dashboard in the format sk-om-v1-. Each operation names the key scope it needs, such as CHAT, EMBEDDINGS, IMAGES, or BILLING_READ. The model endpoints under GET /models are public and need no key. Through Jentic the key is stored by your own instance and attached at call time.

Can I cap how much a single OpenMayhem API request costs?

Yes. Inference endpoints accept the X-OpenMayhem-Max-Cost-Usd header, and further headers cap the input and output price per million tokens. POST /estimates validates a request against live pricing and key limits without a credit hold or charge; the estimate expires after ten minutes and is not a reservation. After the call, GET /requests/{id} returns the settled cost and signed receipt.

What are the rate limits for the OpenMayhem API?

The OpenAPI spec does not publish a numeric limit. It documents a 429 response that asks you to wait the Retry-After seconds before retrying. See https://openmayhem.ai/docs for current limits.

Is there an OpenMayhem MCP server?

You don't need an MCP server to give your agent OpenMayhem. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the inference, job, and model operations on demand without loading another server's tool definitions into its context.

How do I get a chat completion from OpenMayhem through Jentic?

Search Jentic for 'chat completion with a cost cap', load the POST /chat/completions operation, and execute it with model and messages, plus max_tokens to budget the reply. The response follows the OpenAI shape and includes an openmayhem.request_id for GET /requests/{id}. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. For a writing assistant, write a rule that allows POST /chat/completions and GET /requests/{id} only, and the agent can call text models and check what each call cost but cannot start video or music jobs, cancel jobs, or create artifact links. Every call it makes is logged.

OpenMayhem API

AI ReadinessFoundational (D+)50/100

See full scorecard

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

For Agents

Call OpenAI-compatible chat, completion, and embedding models on a decentralised provider network, run image, video, audio, and music generation jobs, and check cost and signed receipts per request.

Use for: I need a chat completion from a model under a fixed cost cap, Generate embeddings for these paragraphs, Find all models with at least a 128k context under a price limit, Check my remaining OpenMayhem credit

Not supported: Does not fine-tune models, host your own weights, or store conversation history. Use for pay-per-use inference and media generation on OpenMayhem's provider network only.

The OpenMayhem API sells pay-per-use AI inference routed across a decentralised network of model providers, with OpenAI-compatible chat completions, completions, responses, and embeddings endpoints. Beyond text, it queues image, video, speech, transcription, audio, and music generation jobs and ComfyUI workflow graphs, which you poll for status, cost, and downloadable artifacts. Billing reserves then settles from prepaid credit, and every request can be looked up afterwards for its settled usage, cost, and provider-signed receipt. Public model endpoints report each model's pricing history, throughput and latency, and provider availability, and request headers let a caller cap cost or require a minimum context size or attestation tier.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

95%

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).

10%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

59%

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

66%

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.

50%

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: CSignals: 1

55%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the OpenMayhem API to your agent

Capabilities

Start building with OpenMayhem API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

OpenMayhem API

Jentic AI Readiness Score

OpenMayhem 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