Install Jentic One Beta

Connect the NinjaChat API to your agent

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

Create chat completions with messages, tools, response_format, and a models list for fallback routing

Send Anthropic-compatible requests to /messages with model, max_tokens, and messages

Generate images from a prompt and start video jobs with duration, aspect_ratio, and reference media

Create embeddings, rerank documents against a query with top_n, and generate speech from text with a chosen voice

GET STARTED

Start building with NinjaChat API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NinjaChat API for, with concrete tasks.

★ Multi-model agent backend through Jentic

An agent that needs a language model for sub-tasks searches Jentic for 'create a chat completion', gets the NinjaChat chat completions schema, and posts messages with a models list so the gateway can fall back if the first model is unavailable. It can read the request trace by ID afterwards to see which model answered and what it cost.

Search Jentic for 'create a chat completion', call POST /chat/completions with messages=[{role:'user',content:'Summarise this ticket'}] and a models list of two model IDs from GET /models, then call GET /requests/{id} for the returned request

Retrieval with embeddings and reranking

Search and question-answering features need both recall and precision. POST /embeddings turns documents into vectors with an optional dimensions setting, and POST /rerank orders candidate documents against a query with top_n and return_documents, so an app can retrieve broadly and then keep only the most relevant passages.

Call POST /rerank with model, query='refund policy for annual plans', documents set to the ten retrieved passages, and top_n=3

Image and video generation

Marketing and content tools can produce visuals from the same account. POST /images/generations takes a prompt with size, n, or aspect_ratio, and POST /videos starts an async video job with duration, aspect_ratio, and optional image_url or reference media; GET /videos/{id} reports progress, and a webhook can announce completion.

Call POST /videos with prompt='slow pan across a mountain lake at dawn', duration=5, aspect_ratio='16:9', then poll GET /videos/{id} until the job completes

Spend control with keys and projects

Teams of one or a few developers still need budgets. The management endpoints, which need a separate management key, create projects with monthlyBudgetCents, issue keys with readOnly, expiresInDays, or their own budget, rotate or revoke keys, and read the audit log, so a runaway script cannot spend past its limit.

Call POST /management/projects with name='support-bot' and monthlyBudgetCents=2000, then POST /management/keys with name='support-bot-prod', the projectId, and expiresInDays=90

Key Endpoints

62 endpoints — the ninjachat api serves chat completions, stateless responses, and anthropic-compatible messages across a list of live models, with routing options and a models array for fallback.

METHOD

PATH

DESCRIPTION

POST

/chat/completions

Create a chat completion

POST

/messages

Create an Anthropic-compatible message

POST

/embeddings

Create embeddings

POST

/images/generations

Generate images

POST

/videos

Create a video job

GET

/models

List live models

POST

/management/keys

Create an API key

POST

/chat/completions

Create a chat completion

POST

/messages

Create an Anthropic-compatible message

POST

/embeddings

Create embeddings

POST

/images/generations

Generate images

POST

/videos

Create a video job

GET

/models

List live models

POST

/management/keys

Create an API key

Why Jentic?

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

Setup

Wiring NinjaChat by hand means tracking which of three credentials each path needs: the inference key as a bearer, the x-api-key header for /messages, and a management key for /management/*. Through Jentic you install once, import NinjaChat from the API Directory, store each key once, and your agent calls it.

Permission scoping

NinjaChat already splits inference keys from management keys, and the key and project ids sit in the URL path (/management/keys/{id}), so a rule can bound your agent to the operations you pick and to one key or project. You choose the operations it may call, so ones like key revocation or project archiving are not included unless you add them.

Credential isolation

Your NinjaChat keys are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a chat completion' or 'rerank documents', and Jentic returns the matching NinjaChat operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using NinjaChat API through Jentic.

What authentication does the NinjaChat API use?

Per its OpenAPI spec, the NinjaChat API uses three credentials. Inference and account endpoints take a NinjaChat API key from the developer console as a bearer token. The /messages endpoint also accepts that key in the `x-api-key` header for Anthropic compatibility. The /management/* endpoints need a separate management key (format nj_mk_...) as a bearer token, and inference keys cannot call them. Public endpoints such as /models, /pricing, /health, and /estimate are open. Through Jentic, each key is stored encrypted by your own Jentic One instance and injected at call time.

Can I use Anthropic-style requests with the NinjaChat API?

Yes. POST /messages is an Anthropic Messages compatibility endpoint that takes model, max_tokens, and messages, with optional system, tools, and stream. OpenAI-style clients use POST /chat/completions instead.

What are the rate limits for the NinjaChat API?

The OpenAPI spec does not specify rate limits. Spend is metered instead: chat and responses bill actual token usage, images and videos use per-unit pricing, and project and key budgets cap spend. Check https://www.ninjachat.ai/developers for current limits.

How do I generate an image with the NinjaChat API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add NinjaChat from the Jentic API Directory, and store your NinjaChat API key. Your agent searches for 'generate an image', calls POST /images/generations with a prompt and size, and can call POST /estimate first to preview the cost. 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 NinjaChat API?

Yes. Store only the inference key, and write a rule that allows POST /chat/completions, POST /embeddings, and GET /models. The agent can then call models and read the model list, but it cannot start video jobs, register webhooks, or reach any /management/* operation, since it holds no management key.

Is there a NinjaChat MCP server?

You don't need an MCP server to give your agent the NinjaChat API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it, discovering operations on demand rather than loading all of them into its context.

Can I see how much a NinjaChat request will cost before sending it?

Yes. POST /estimate is a public pre-flight estimate that does not deduct credits, and GET /pricing returns the live price sheet. After a call, GET /requests/{id} returns the request trace.

NinjaChat API

AI ReadinessFoundational (D)43/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer, apiKey62 EndpointsREST

For Agents

Call many chat models through one OpenAI-style or Anthropic-style endpoint, generate images, video, speech, and embeddings, rerank documents, search the web, and manage keys, projects, budgets, and webhooks.

Use for: I need to send the same prompt to a fallback list of models, Generate a 1024x1024 product image from a text prompt, Create embeddings for a batch of support articles, Rerank these search results against the user's question

Not supported: Does not fine-tune or host custom models, store files for retrieval, or provide a vector database. Use for calling hosted chat, image, video, speech, embedding, rerank, and search models through one NinjaChat account only.

The NinjaChat API serves chat completions, stateless responses, and Anthropic-compatible messages across a list of live models, with routing options and a models array for fallback. Alongside text it generates images and video jobs, speech, embeddings, document reranking, and web search, and it can compare several chat models side by side, run batches, and chain up to five dependent chat, image, and video steps as one async pipeline. Account tooling covers usage, balance, request traces, saved presets, webhooks for video completion and spend alerts, and a separate management surface for API keys, projects, budgets, and audit logs. Chat and responses bill actual token usage, while images and videos use per-unit pricing.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

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

14%

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.

70%

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

23%

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.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

92%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

57%

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: C+Signals: 1

59%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the NinjaChat API to your agent

Capabilities

Start building with NinjaChat API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

NinjaChat API

Jentic AI Readiness Score

NinjaChat 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