Install Jentic One Beta

Connect the Meta Agent Tools to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Meta Agent Tools, 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%2Fapp.br%2Fapp" | 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%2Fapp.br%2Fapp" | 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 Meta Agent Tools API.

Search the public directory of Model Context Protocol servers, agent skills, and plugins

Read a remote server's security review, measured signals, and change history

Check a server address before installing it using signals already collected

GET STARTED

Start building with Meta Agent Tools API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Meta Agent Tools API for, with concrete tasks.

★ Agent-Vetted Tool Discovery

An AI agent connected through Jentic searches the directory for a server that matches a task, reads its security review and announced tools, and only then decides whether to install it. Because the directory returns a measured security level and the signals behind it, the agent can screen out risky servers instead of installing whatever it finds first.

Search the directory for a server that sends Slack messages, read its security review, and report whether its level is safe to install

Publishing a Tool Listing

A maintainer registers a Model Context Protocol server, skill, or plugin as a listing so other developers and agents can discover it. The listing enters as pending for moderation, and editing its public content sends it back for review, so the directory stays curated rather than open spam.

Monitoring Installed Agent Tools

A team runs a private monitor project that records which servers and skills an agent has installed and the inventory changes each installation reports, then links those items to the directory watches that review them. This gives an operator one place to see what an agent is running and whether any of it has changed security posture.

List the installed inventory for a monitoring project and flag any item whose linked security review has changed

Key Endpoints

146 endpoints — the meta agent tools api indexes model context protocol servers, agent skills, and plugins in a public, searchable directory and runs security reviews of remote servers before an agent installs them.

METHOD

PATH

DESCRIPTION

GET

/api/listings

Search the public listings

POST

/api/listings

GET

/api/listings/{id}

Get one listing

GET

/api/listings/{id}/security

Get a listing's security review

GET

/api/check

Check a server address before installing

GET

/api/facets

Get directory counts by kind, provenance, and category

GET

/api/listings

Search the public listings

POST

/api/listings

GET

/api/listings/{id}

Get one listing

GET

/api/listings/{id}/security

Get a listing's security review

GET

/api/check

Check a server address before installing

GET

/api/facets

Get directory counts by kind, provenance, and category

Why Jentic?

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

Setup

Wiring the Meta Agent Tools API by hand means juggling several token types (a guest token, an account API key, and an agent wallet credential), sorting public endpoints from authenticated ones, and signing an x402 payment header for metered calls. Through Jentic you install once, import it from the API Directory, store your token once, and your agent calls it.

Permission scoping

You choose which operations your agent may call, so you can allow browsing listings and reading security reviews while leaving listing creation, comments, and watch purchases out. The listing and monitoring-project ids travel in the URL path, so a rule can also bound the agent to one listing or one project.

Credential isolation

Your Meta Agent Tools 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 'find a tool server for email' or 'read a server's security review', and Jentic returns the matching Meta Agent Tools operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Meta Agent Tools API through Jentic.

Is there a Meta Agent Tools MCP server?

Yes. Meta Agent Tools exposes its own Model Context Protocol endpoint. You can also connect it directly through Jentic: your agent gets the directory's full 146-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.

Can I limit what my agent is allowed to do with the Meta Agent Tools API?

Yes. Write a rule that allows only the listing-search and security-review read operations, so the agent can discover and vet tools but cannot create listings, post comments, or buy watch slots, and every call it makes is logged. Because listing and monitoring-project ids sit in the URL path, you can also pin the agent to a single listing or project.

What authentication does the Meta Agent Tools API use?

The Meta Agent Tools API authenticates with bearer tokens (a guest token, an account API key, or an agent wallet credential) plus an API key header for x402 per-call payments, per its OpenAPI spec. Many browse and read endpoints are public and need no token. Through Jentic the token is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

Can I check a server's security before my agent installs it?

Yes. The security review for a listing returns the remote server's measured level, the signals behind it, the tools it announced at its last check, and any changes since. A separate pre-install check reports what the directory already knows about a server address without visiting it, so an agent can screen a tool before adding it.

What are the rate limits for the Meta Agent Tools API?

The OpenAPI spec does not publish a global rate limit for the Meta Agent Tools API. It does cap comment writes at 20 per hour per owner, and watch capacity is governed by your plan; for other limits, see the Agentalog documentation at https://agentalog.com.

How do I discover and vet agent tools with the Meta Agent Tools API through Jentic?

Import the Meta Agent Tools API from the Jentic API Directory, then have your agent issue a request such as 'search the directory for a GitHub tool server and read its security review'. Jentic matches the intent to the search and security-review operations and returns their input schemas so the agent builds the right calls, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Br Meta Agent Tools

AI ReadinessFoundational (C)56/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsPackage Registrybearer, apiKey146 EndpointsREST

For Agents

Search a directory of MCP servers, agent skills, and plugins, read their security reviews, and register or monitor listings. Authenticates with a bearer token, an account API key, or an agent wallet credential; many browse endpoints are public.

Use for: Find a Model Context Protocol server for sending email, Search the directory for agent skills by category, Check whether a remote tool server is safe to install, Read the security review for a listing

Not supported: Does not host or execute the listed servers, run their tools, or manage your agent runtime. Use for discovering, reviewing, and monitoring agent tool listings only.

The Meta Agent Tools API indexes Model Context Protocol servers, agent skills, and plugins in a public, searchable directory and runs security reviews of remote servers before an agent installs them. You can browse and search listings by kind, provenance, and category, register your own server or skill for moderation, and read a listing's measured security level, announced tools, and README. It also exposes feeds, index signals from external rating sources, and a private monitor that tracks the tools a given agent project has installed and the inventory changes they report.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D-Signals: 4

66%

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

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.

95%

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

93%

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

78%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

97%

OperationId Quality

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

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: B+Signals: 1

69%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

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

49%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Meta Agent Tools to your agent

Capabilities

Start building with Meta Agent Tools API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Br Meta Agent Tools

Jentic AI Readiness Score

Meta Agent Tools

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