Skip to main content
KEPAiX
INTELLIGENCE PLATFORM
PUBLIC PROJECT
AI Agent And x402 Quick Start

Build Your First
KepAIx Integration

Request. Inspect 402. Pay. Receive Protected JSON.
Start with a verified KepAIx premium endpoint, inspect its live machine-readable payment requirements, complete an Algorand Mainnet USDC payment, and receive structured educational intelligence. The fastest human-operated path uses the live Browser Marketplace, while autonomous clients can implement the same x402 flow programmatically. KepAIx is educational only. Payment unlocks a documented resource and does not guarantee accuracy, value, profit, certainty, or future outcomes.
~5 MinQuick start path
HTTP 402Payment required
x402 v2Payment protocol
USDCAlgorand Mainnet
2Premium products
JSONProtected response
The Complete Flow

Five Steps From Discovery To Protected JSON

The protocol is simple: choose a verified resource, request it, inspect the HTTP 402 response, complete the listed payment, and validate the returned settlement evidence and JSON.

1
ChooseSelect Market Regime Intelligence or Atlas Premium Intelligence.
2
RequestSend an initial GET request to the selected premium endpoint.
3
Inspect 402Read the live machine-readable payment requirements.
4
Pay And VerifyCreate the payment payload, sign it, and retry the request.
5
Receive JSONValidate settlement evidence and use the protected response carefully.
Choose A Product

Two Verified Premium Resources

Both products use HTTP 402 and x402 v2. Always inspect the live payment requirements returned by the endpoint instead of permanently hard-coding terms into production clients.

x402 Market Regime Intelligence

Focused premium educational market-regime intelligence and the verified upgrade path from the free Market Regime API.

KEP-X402-001 0.01 USDC 10000 Atomic Units Algorand Mainnet
https://kepaix.com/api/x402-market-regime.php Inspect HTTP 402 — Opens in New Window

Atlas Premium Intelligence

Broader structured educational synthesis of verified KepAIx intelligence. Public response schema version 0.1.0.

KEP-X402-002 0.02 USDC 20000 Atomic Units Algorand Mainnet
https://kepaix.com/api/x402-atlas.php Inspect HTTP 402 — Opens in New Window
Current verified asset: USDC on Algorand Mainnet, ASA 31566704. Payment terms can evolve, so production integrations should always trust the live HTTP 402 requirements returned by the selected endpoint.
Fastest Human Path

Use The Live Browser Marketplace

The Browser Marketplace is the easiest production reference path for a person. It lets you complete the full flow without first writing a client.

What You Do

Select Market Regime or Atlas, connect Pera Wallet, request the resource, review the listed USDC price, approve the payment, and receive protected JSON.

Open Browser Marketplace

What It Demonstrates

Product selection, wallet connection, HTTP 402 discovery, payment approval, Algorand settlement, payment verification, and protected resource delivery through one shared purchase engine.

Developer Request

Start By Inspecting HTTP 402

An unpaid request is supposed to return HTTP 402. In an x402 workflow, that is the protocol response that tells the client how to continue.

Initial Atlas Request
curl -i \
  -H "Accept: application/json" \
  https://kepaix.com/api/x402-atlas.php
Expected Result HTTP 402 Payment Required with machine-readable payment metadata describing the gated resource and its current payment requirements.
HTTP 402
Simplified JavaScript Inspection
const response = await fetch(
  "https://kepaix.com/api/x402-atlas.php",
  { headers: { Accept: "application/json" } }
);

if (response.status !== 402) {
  throw new Error(`Expected HTTP 402, received ${response.status}`);
}

const paymentRequired =
  response.headers.get("PAYMENT-REQUIRED");

if (!paymentRequired) {
  throw new Error("Missing PAYMENT-REQUIRED header");
}

// Decode and validate the live payment requirements
// before constructing any payment payload.
Programmatic Flow

The Verified x402 Client Sequence

The current KepAIx Atlas test client follows this sequence. Public examples should never include private keys, local environment values, push secrets, or protected server logic.

GET Premium EndpointRequest Atlas or Market Regime
Decode PAYMENT-REQUIREDRead and validate live payment requirements
Create Payment PayloadUse the required network, asset, amount, and recipient
Create PAYMENT-SIGNATUREAuthorize the payment through the client wallet
Retry GET RequestAttach the payment signature to the same resource request
Decode PAYMENT-RESPONSEValidate settlement evidence returned by the server
Read Protected JSONValidate version, timestamps, confidence, limitations, and disclaimer
Protected Response

What The Premium Resource Provides

Payment unlocks the selected documented educational resource. It does not guarantee that every optional field is populated in every response.

Market Regime Intelligence

Focused premium regime context designed as the verified paid counterpart to the free Market Regime API.

Atlas Premium Intelligence

May include executive summary, market environment, cross-system synthesis, evidence, contradictions, confidence, risk context, historical context, educational interpretation, limitations, disclaimer, and metadata.

Defensive Integration

Validate Before You Trust The Response

Machine-payable access does not remove the need for defensive integration. Validate both the payment protocol and the returned educational data.

HTTP StatusConfirm the expected unpaid, paid, and error responses.
Content TypeConfirm the response is the expected machine-readable format.
x402 VersionValidate the protocol contract supported by the client.
Resource IdentityConfirm the endpoint and product match the intended request.
NetworkValidate the network declared by the live payment requirements.
Asset And AmountVerify the asset identifier and exact requested amount.
RecipientValidate the live payment recipient before authorization.
SettlementConfirm the payment response indicates successful verification and settlement.
SchemaValidate the response version or Atlas schema before use.
FreshnessInspect timestamps and freshness indicators.
ConfidenceDo not convert confidence into certainty.
LimitsPreserve limitations, disclaimers, and unavailable-data conditions.
Verified Production Evidence

What KepAIx Can Truthfully Demonstrate

The following statements are limited to verified production behavior and do not imply unsupported adoption, uptime, revenue, customer, or performance claims.

Live Premium EndpointsBoth verified premium endpoints are publicly available.
Valid HTTP 402Unpaid access intentionally returns HTTP 402 Payment Required.
Mainnet PaymentsAlgorand Mainnet USDC purchases have completed successfully.
Protected DeliveryProtected JSON has been returned after successful verification and settlement.
Browser ReferenceThe Browser Marketplace demonstrates the production purchase path.
Verified PricingMarket Regime is 0.01 USDC and Atlas Premium is 0.02 USDC.
Quick Start FAQ

What Builders Should Know

These answers are written for developers, autonomous clients, technical reviewers, and x402 challenge judges.

What is the fastest way to test KepAIx?Open the Browser Marketplace, select a product, connect Pera Wallet, approve the listed payment, and receive protected JSON.
Is HTTP 402 an error?For an unpaid x402 request, HTTP 402 is the expected protocol response that tells the client how to continue.
Should I hard-code the payment terms?No. Read and validate the live requirements returned by the selected endpoint.
Does payment guarantee accuracy?No. Payment unlocks a documented educational resource and does not guarantee accuracy, certainty, value, or profit.
Can an AI agent use the same flow?Yes. An autonomous client can inspect the HTTP 402 requirements, construct the supported payment payload, retry the request, and validate the response.
Is KepAIx financial advice?No. KepAIx provides educational market intelligence only and does not provide financial, investment, trading, legal, or tax advice.

Start With One Real Request

Use the browser reference to see the complete production flow, inspect a live HTTP 402 response, or continue into the full API documentation for endpoint contracts and examples.