Install Jentic One Beta

Connect the MIDAX402 to your agent

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

Look up whether MIDAX holds a signed conformance verdict for a URL before paying it, free, with verify-before-pay

Probe an x402 endpoint with pulse for an x402_live, x402_challenge_malformed, inconclusive, or unreachable verdict

Run a private x402 conformance check with verdict, raw evidence, and a fix list through verify

Publish a permanent EIP-712 signed attestation of an endpoint to the public record with attest

GET STARTED

Start building with MIDAX402 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MIDAX402 API for, with concrete tasks.

★ Verify before your agent pays, through Jentic

An agent about to pay an unfamiliar x402 service first asks MIDAX402 whether a signed verdict exists. Through Jentic it calls verify-before-pay, which reads only MIDAX's signed registry and fails closed: an endpoint with no attestation comes back as unverified with a null conformance_verdict. Your Jentic One rules decide whether the agent may go on to the paid pulse or verify operations.

GET /midas-ops/verify-before-pay with url 'https://api.example.com/paid-endpoint'; if status is 'unverified', skip the payment and report it

Conformance testing for your own x402 service

Builders of x402 services can test their 402 challenge and price coherence against their discovery doc. The verify operation returns the verdict, raw evidence, and a fix list privately, without signing or publishing anything, at $0.10 per call. When the service passes, attest publishes the same check as a permanent signed public record at $0.50.

POST /midas-ops/verify with url 'https://myservice.example.com/api/quote', read the fix list, and repeat after each fix until the verdict passes

Live status checks of paid endpoints

Pulse answers whether an x402 endpoint is live and charging right now, returning the verdict, HTTP status, checked_at, and age_seconds for $0.001. Results are cached per target for up to 60 seconds, so paying buys the current answer rather than a fresh probe.

GET /midas-ops/pulse with url 'https://api.example.com/paid-endpoint' and retry the target only if the verdict is x402_live

x402 Global Challenge readiness

Participants in the x402 Global Challenge can see the five official requirements for their endpoint as pass, fail, or not_measured with the free challenge-check preview, then buy the EIP-712 signed challenge-check verdict for $1.00.

GET /midas-ops/challenge-check/preview with url 'https://myservice.example.com/api', and if every requirement passes, POST /midas-ops/challenge-check with the same url

Key Endpoints

39 endpoints — the midax402 api checks x402 pay-per-call services against the x402 spec and signs its verdicts so anyone can verify them without asking midax.

METHOD

PATH

DESCRIPTION

GET

/midas-ops/verify-before-pay

Free signed-registry lookup before paying

GET

/midas-ops/pulse

Live x402 status verdict

POST

/midas-ops/verify

Private conformance check

POST

/midas-ops/attest

Publish a signed attestation

GET

/badge

Embeddable verdict badge

POST

/midas-ops/basic

Basic tier analysis

GET

/midas-ops/semantic-discovery

Free corpus preview

GET

/midas-ops/verify-before-pay

Free signed-registry lookup before paying

GET

/midas-ops/pulse

Live x402 status verdict

POST

/midas-ops/verify

Private conformance check

POST

/midas-ops/attest

Publish a signed attestation

GET

/badge

Embeddable verdict badge

POST

/midas-ops/basic

Basic tier analysis

GET

/midas-ops/semantic-discovery

Free corpus preview

Why Jentic?

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

Setup

Wiring MIDAX402 by hand means sending an x402 payment proof in the PAYMENT-SIGNATURE header, telling paid routes from free ones, and allowing long client timeouts on analysis tiers. Through Jentic you install once, import MIDAX402 from the API Directory, and your agent calls it with each operation's schema in hand.

Permission scoping

MIDAX402 carries the target URL in a query parameter or the request body, so rules bound which operations your agent may call, not which targets it checks. Limit the agent to the operations it needs, such as verify-before-pay and pulse, so permanent attestations and rank purchases are not included unless you add them.

Credential isolation

MIDAX402's paid routes are authorised per request by an x402 payment proof rather than a long-lived API key, so there is no standing secret for the agent to hold. Calls still run through your own Jentic One instance, where your rules and logs apply.

Intent-based discovery

Agents search Jentic by intent such as 'is this x402 endpoint live' or 'verify a paid API before paying', and Jentic returns the matching MIDAX402 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MIDAX402 API through Jentic.

What authentication does the MIDAX402 API use?

Per its OpenAPI spec, MIDAX402's paid operations use the x402Payment scheme: an apiKey-style header named PAYMENT-SIGNATURE carrying an x402 payment proof, and some SDKs send X-PAYMENT instead. Several operations need no auth or payment, including verify-before-pay, the challenge-check preview, semantic-discovery, the badge, the anchor, and contact-map. The metrics route is keyed with a key query parameter.

How much does MIDAX402 charge?

Prices are per call in USDC, as declared in the spec: pulse $0.001, basic $0.03, standard $0.05, premium $0.07, market_brief $0.15, verify $0.10, attest $0.50, challenge-check $1.00, and authenticity-report $5.00. Rank steps on the verification board run from 1 to 100 USDC. Payment is accepted on Base Mainnet, Algorand Mainnet, and Solana Mainnet.

How do I check an x402 endpoint through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh` and import MIDAX402 from the directory. Your agent searches 'verify an x402 endpoint before paying', gets GET /midas-ops/verify-before-pay with its schema, and sends the target url; no payment is needed for that lookup. 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 MIDAX402 API?

Yes. For example, allow only GET /midas-ops/verify-before-pay and GET /midas-ops/pulse, so the agent can check endpoints before it pays them but cannot publish a permanent attestation, buy rank positions, or order a $5.00 authenticity report. Every call it makes is logged.

Is there a MIDAX402 MCP server?

You don't need an MCP server to give your agent MIDAX402. Jentic connects it directly from the API Directory: import it and your agent calls it, discovering operations on demand instead of loading extra tool definitions into its context.

What are the rate limits for the MIDAX402 API?

The spec does not give numeric rate limits. It states that semantic-discovery is IP rate limited and that pulse serves a short-lived cached answer per target so busy endpoints are not hammered. Check the MIDAX402 documentation at https://midax402.com for current limits.

Is a MIDAX402 attestation public?

Yes. The attest operation publishes a permanent public record at /midas-ops/attestations, signed with EIP-712, and publishes whatever it finds, including non-conformant or unreachable results. Use verify first to see the same check privately.

MIDAX402

AI ReadinessFoundational (D)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsTesting QaapiKey (x402 payment, PAYMENT-SIGNATURE header)39 EndpointsREST

For Agents

Check whether an x402 endpoint is live and conformant before your agent pays it, using MIDAX402's pulse, verify, and signed-registry lookups.

Use for: Check whether this x402 endpoint is verified before I pay it, Is this paid API live and charging right now?, Run a private conformance check on my x402 service, I want to publish a signed attestation for my endpoint

Not supported: Does not process payments for you, host x402 services, or give financial advice. Use for verifying x402 endpoints and querying its curated x402 corpus only.

The MIDAX402 API checks x402 pay-per-call services against the x402 spec and signs its verdicts so anyone can verify them without asking MIDAX. An agent can ask whether an x402 endpoint is live and charging right now, get a private conformance check with raw evidence and a fix list, or publish a permanent signed attestation. Before paying an unfamiliar service, a free verify-before-pay lookup reads MIDAX's signed registry, and an embeddable SVG badge shows an endpoint's verdict. It also sells non-personalized analysis tiers and market briefs over a curated x402 corpus, paid in USDC per call.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

81%

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

19%

Example Density

How richly the API is illustrated with examples.

78%

Example Validity

Percentage of examples that conform to their schemas.

49%

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

51%

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.

62%

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

50%

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

47%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MIDAX402 to your agent

Capabilities

Start building with MIDAX402 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MIDAX402

Jentic AI Readiness Score

MIDAX402

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