Install Jentic One Beta

Connect the AISkills402 to your agent

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

Browse the skill listing with the price and buy URL for each SKILL.md file

Read a skill card showing its price, bundled tests, outline, and version history

Buy an individual SKILL.md file as a one-time x402 purchase in USDC on Base

Buy a discounted pack of ten to two hundred skill files chosen at once

Re-download a purchased file and its future versions for free with the purchase token

GET STARTED

Start building with AISkills402 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AISkills402 API for, with concrete tasks.

★ Agent Buys a Skill On Demand

When an agent hits a task it has no playbook for, such as repairing broken JSON or writing a changelog from commits, it can list the available skills, read the card to confirm the price and tests, and buy the matching SKILL.md file as a one-time USDC purchase on Base. Because the file is the product and there is no account, the agent downloads a self-contained skill it keeps forever. This lets an agent acquire a vetted capability at the moment it needs it rather than carrying every skill up front.

List the skills for sale, read the card for the JSON Repair skill to confirm its price and tests, then buy its SKILL.md file as a one-time USDC purchase.

Browsing Skills and Prices Before Buying

A buyer can read the full listing with each skill's price and buy URL, then open individual cards that show the bundled tests, an outline of what the skill does, and its version history. Nothing requires an account, so an agent or a person can evaluate the catalogue of skills and decide what is worth purchasing before spending anything. The per-skill tests make it clear what each skill is checked to do.

Read the skill listing, then open the cards for three skills and compare their prices, bundled tests, and version histories.

Re-downloading Purchases and Updates

Every purchase yields a token that an agent can use to re-download the SKILL.md file for free, including any new versions published later. This means an integration never has to re-buy a skill to pick up an update, and a lost local copy is recoverable from the token alone. For long-running agents it provides a stable way to keep acquired skills current.

Use a saved purchase token to re-download the latest version of a previously bought SKILL.md file.

Key Endpoints

121 endpoints — the aiskills402 api sells ready-made skill.

METHOD

PATH

DESCRIPTION

GET

/v1/skills

List the skills for sale with prices and buy URLs

GET

/v1/skills/{slug}

One skill card: price, tests, outline, versions

GET

/v1/skills/code-review/file

Buy the Code Review skill file

GET

/v1/skills/json-repair/file

Buy the JSON Repair skill file

GET

/v1/packs/file

Buy a discounted pack of skill files

GET

/v1/purchases/{token}

Re-download a purchased file and its future versions for free

GET

/health

Report whether the store is currently selling

POST

/a2a

Agent-to-agent receptionist answering catalogue questions

GET

/v1/skills

List the skills for sale with prices and buy URLs

GET

/v1/skills/{slug}

One skill card: price, tests, outline, versions

GET

/v1/skills/code-review/file

Buy the Code Review skill file

GET

/v1/skills/json-repair/file

Buy the JSON Repair skill file

GET

/v1/packs/file

Buy a discounted pack of skill files

GET

/v1/purchases/{token}

Re-download a purchased file and its future versions for free

GET

/health

Report whether the store is currently selling

POST

/a2a

Agent-to-agent receptionist answering catalogue questions

Why Jentic?

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

Setup

Wiring the AISkills402 API by hand means handling its x402 payment flow for each buy, where a bare request answers with the payment requirements and you sign and retry, and tracking purchase tokens for free re-downloads. Through Jentic you install once, import it from the API Directory, and your agent browses the listing and completes purchases without you hand-wiring the payment handshake.

Permission scoping

The free listing and skill-card reads can be allowed on their own, so a rule lets your agent browse skills and prices without spending. Each paid buy operation settles USDC over x402, so you add only the specific purchase operations a task needs; slugs travel in the URL path (/v1/skills/{slug}), so rules bound which operations run.

Credential isolation

AISkills402 needs no account and no API key, so there is nothing to store. Your agent reaches it through your own Jentic One instance, which keeps every request and any x402 payment signing on your own infrastructure rather than in the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list skills for sale' or 'buy a code review skill', and Jentic returns the matching AISkills402 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using AISkills402 API through Jentic.

What authentication does the AISkills402 API use?

Per its OpenAPI spec the AISkills402 API uses no account and no API key: what is sold is the SKILL.md file itself, as a one-time purchase in USDC on Base over x402. A purchase returns a token you use to re-download the file and future versions for free, so the token is a receipt rather than a login credential.

What can I buy with the AISkills402 API?

You can buy individual SKILL.md files covering tasks such as code review, JSON and YAML repair, translation, SEO metadata, and many more, each delivered as a self-contained file you keep forever. You can also buy a discounted pack of ten to two hundred skills chosen at once, and re-download anything you have purchased for free.

What are the rate limits for the AISkills402 API?

The OpenAPI spec does not publish rate limits for the AISkills402 API; the listing and skill-card reads are lightweight, and the health operation reports whether the store is currently selling. For current limits check the vendor documentation at https://aiskills402.com.

How do I buy a skill file with the AISkills402 API through Jentic?

Import the AISkills402 API from the Jentic API Directory, then have your agent search by intent such as 'buy a skill file' and Jentic returns the matching buy operation with its input schema. The agent reads the skill listing, confirms the price on the card, and completes the one-time USDC purchase. 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 AISkills402 API?

Yes. The free listing and skill-card reads can be allowed on their own, so a rule lets your agent browse skills and prices but not spend. Because each buy operation settles USDC over x402, you add only the specific purchase operations a task needs rather than blanket purchase access, and every call it makes is logged.

Is there an AISkills402 MCP server?

You don't need an MCP server to give your agent the AISkills402 API. Jentic connects it directly from the API Directory: import it, and your agent calls the listing, card, and buy operations on demand without loading another server's tool definitions into its context.

Do I keep a skill file after buying it from the AISkills402 API?

Yes. The SKILL.md file is the product, bought once in USDC on Base, and you keep it forever. The purchase token lets you re-download it and any future versions for free, so an update never requires buying the skill again.

AISkills402

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsPackage Registrynone121 EndpointsREST

For Agents

Browse and buy ready-made SKILL.md files for AI agents as one-time USDC purchases on Base, with no account or key. List skills with prices, read per-skill cards with tests and versions, buy single files or discounted packs, and re-download purchases for free.

Use for: List the skills for sale with their prices, Show me the card for a specific skill, including its tests and versions, Buy the code review SKILL.md file, Purchase a discounted pack of skill files

Not supported: Does not host, execute, or run the skills it sells, and it manages no account. Use for browsing and buying SKILL.md skill files for AI agents only.

The AISkills402 API sells ready-made SKILL.md files for AI agents as one-time purchases in USDC on Base, with no account and no API key. It lists the available skills with their prices and buy URLs, serves a card for each skill showing its price, bundled tests, outline, and versions, and delivers the chosen SKILL.md file on purchase. Buyers keep each file forever, re-download it and future versions for free using a purchase token, and can buy a discounted pack of many skills at once. An agent-to-agent receptionist endpoint answers messages about what is for sale.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

94%

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

100%

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.

73%

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

80%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

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

78%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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

38%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AISkills402 to your agent

Capabilities

Start building with AISkills402 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AISkills402

Jentic AI Readiness Score

AISkills402

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