Install Jentic One Beta

Connect the Made Agent Access API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Made Agent Access 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%2Fmade.app%2Fmade" | 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%2Fmade.app%2Fmade" | 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 Made Agent Access API.

Initialize a JSON-RPC 2.0 session with Made and receive an Mcp-Session-Id for later calls

List the tools Made currently offers with a tools/list request instead of hardcoding them

Invoke a Made tool with a tools/call request carrying the tool name and its arguments object

Open a Server-Sent Events stream to receive server-to-client messages for a live session

GET STARTED

Start building with Made Agent Access API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Made Agent Access API for, with concrete tasks.

★ AI agent calling Made tools through Jentic

A developer wants their agent to use Made's tools without hand-building the OAuth 2.1 PKCE flow. Through Jentic the agent searches for 'call a Made tool', loads the JSON-RPC request operation, and sends a tools/list request to see what is available before a tools/call with the chosen tool name and arguments. The OAuth token is injected at call time by the developer's own instance.

POST a JSON-RPC initialize request, then a tools/list request with the returned Mcp-Session-Id, then a tools/call request naming one listed tool with its arguments

Runtime tool discovery

Made asks clients to discover tools at runtime rather than from a fixed list, so the set can change without a client update. A tools/list request returns the current tools for the session, and a client can cache them for the length of that session. This keeps an integration in step with whatever Made currently offers.

Send a JSON-RPC request with method tools/list on an initialized session and return each tool name it lists

OAuth configuration discovery

Before requesting a token, a client needs the authorization server and the scopes the resource accepts. GET on the well-known oauth-protected-resource path is public and returns resource, authorization_servers, and scopes_supported, so a client can build its authorization code request with PKCE from live metadata rather than copied values.

Call GET /.well-known/oauth-protected-resource and report the authorization_servers and scopes_supported values

Key Endpoints

4 endpoints — the made agent access api carries json-rpc 2.

METHOD

PATH

DESCRIPTION

POST

/mcp

Send a JSON-RPC request

GET

/mcp

Open a Server-Sent Events stream

DELETE

/mcp

Close a session

GET

/.well-known/oauth-protected-resource

Get OAuth protected-resource metadata

POST

/mcp

Send a JSON-RPC request

GET

/mcp

Open a Server-Sent Events stream

DELETE

/mcp

Close a session

GET

/.well-known/oauth-protected-resource

Get OAuth protected-resource metadata

Why Jentic?

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

Setup

Wiring Made by hand means running an OAuth 2.1 authorization code flow with PKCE, refreshing tokens, and carrying a session id header across JSON-RPC calls. Through Jentic you install once, import Made from the API Directory, authorize once, and your agent calls it.

Permission scoping

Made sends every tool call to the same JSON-RPC operation with the tool name in the request body, so rules bound which operations your agent may call, such as sending requests or closing sessions, not which Made tool it invokes. You choose the operations it may call, so session close is not included unless you add it.

Credential isolation

Your Made OAuth token 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 'call a Made tool' or 'list Made tools', and Jentic returns the matching Made operation with its input schema, including the JSON-RPC request shapes, so the agent builds a valid call first time.

FAQs

Specific to using Made Agent Access API through Jentic.

What authentication does the Made Agent Access API use?

Made declares OAuth 2.1 with the authorization code flow and PKCE in its OpenAPI spec, with tokens from www.made.app and scopes such as openid, offline_access, media:read, media:write, generations:read, generations:write, and billing:read. The session operations require the token, while GET /.well-known/oauth-protected-resource is public. Through Jentic the token is stored by your own instance and attached at call time.

Is there a Made MCP server?

Yes. Made runs an official remote MCP server, and this spec describes its transport. You can also connect it through Jentic: your OAuth token is injected at call time by your self-hosted instance instead of living in a client config file, your rules decide which operations the agent may call, each call the agent makes is logged, and connecting your next API is an import rather than another install and auth setup.

How do I find out which tools Made offers?

Send a JSON-RPC request with method tools/list on an initialized session. Made asks clients to discover tools this way at runtime, so the list reflects what Made currently provides rather than a fixed set in the spec.

What are the rate limits for the Made Agent Access API?

The OpenAPI spec does not specify rate limits. Check the Made connector documentation at https://www.made.app/mcp for current limits.

How do I call a Made tool through Jentic?

Search Jentic for 'call a Made tool', load the JSON-RPC request operation, and send initialize, then tools/list, then tools/call with the tool name and arguments, reusing the Mcp-Session-Id header between calls. 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 Made Agent Access API?

Partly. For example, a rule that allows the JSON-RPC request and event-stream operations but not session close lets the agent work in a session without ending it. Tool names travel inside the request body, so a rule cannot allow one Made tool and block another; narrow that with the OAuth scopes you grant, such as read-only media:read. Jentic logs each call the agent makes.

Made App Made Agent Access API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLMl Inferenceoauth24 EndpointsREST

For Agents

Call the tools Made exposes to agents over JSON-RPC: initialize a session, list available tools, invoke a tool by name with arguments, and stream results, authorized with Made OAuth.

Use for: List all tools Made makes available to my agent, I need to call a Made tool with specific arguments, Check which OAuth scopes the Made endpoint supports, Open an event stream for my current Made session

Not supported: Does not publish a fixed REST endpoint per tool, and does not handle account sign-up or token management. Use for reaching Made's agent tools over JSON-RPC only.

The Made Agent Access API carries JSON-RPC 2.0 requests to the remote agent tool server that Made runs for AI clients. A client initializes a session, lists the tools Made currently offers with tools/list, and invokes one with tools/call by passing a tool name and an arguments object, then reads results as JSON or as a Server-Sent Events stream. Sessions are tracked with a session id header returned at initialization and can be closed explicitly. A public protected-resource metadata document tells a client which authorization server and scopes, such as media:read, generations:write, and billing:read, the endpoint expects.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

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.

44%

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

28%

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

90%

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: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Made Agent Access API to your agent

Capabilities

Start building with Made Agent Access API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Made App Made Agent Access API

Jentic AI Readiness Score

Made Agent Access 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