Repository avatar
AI Tools
v3.1.2
active

fresh402

io.github.kirillradchenko96/fresh402

Four web/API/Base workflows, 11 paid MCP/REST tools; x402 USDC Base/Solana, MPP Base, prepaid.

Documentation

Fresh402 — complete intelligence workflows for autonomous agents

Start with the walletless Check guide, read-only network eligibility, or fixed real-code Website and API fixtures. Fixtures do not fetch live sources, mutate customer state or charge money. Reuse a free Register baseline in an explicitly authorized workflow. The live release identity distinguishes product, contract, registry metadata and SDK versions.

Four server workflows turn website, API and finalized Base tasks into structured evidence: Website Change Intelligence, API Compatibility Review, On-chain Evidence Brief and Cross-domain Release Evidence. One authorized operation combines its internal stages, with reusable observations and exact original-result recovery. Seven focused paid tools and free Register remain available through REST and MCP.

Hosted API 3.1.0. This repository contains public documentation and source clients; the hosted backend remains private. Choose a workflow · Working inputs and state · Start free.

Start without spending

Read live discovery. Discovery makes no payment. For a free persistent baseline:

curl https://api.fresh402.com/v1/register \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://example.com/"}'

Save the actual returned watch_id and hash. Repeating the same canonical URL and rules returns existing state without another fetch or refresh. Registration has source, rate and capacity limits. Smart Diff uses a saved watch. OpenAPI Diff accepts a saved watch or an explicit contracts:{before,after} pair; Check also accepts a URL directly.

For one eligible walletless Check, inspect instant_evaluation.enabled and send {"url":"https://example.com/","evaluation":true} to Check. One attempted Check per verified network prefix per approved resource period; exact replay returns retained evidence, not a new observation. No automatic payment after 429. Standard clients.

The separate machine trial requires an unfunded EOA ownership signature, no human CAPTCHA: up to 100 Checks (20/day) plus bounded samples when enabled. New credentials last at most 30 days; existing identities retain their original allowance and expiry. Human Web trials additionally require human verification. Live availability is not reserved execution capacity.

Connect MCP or REST

Canonical MCP: https://api.fresh402.com/mcp (Streamable HTTP). For clients using the common configuration format:

{"mcpServers":{"fresh402":{"type":"http","url":"https://api.fresh402.com/mcp"}}}

Client configuration formats vary; see MCP initialization, schemas and credentials. Connecting alone grants no signing or payment authority. REST uses https://api.fresh402.com; the live OpenAPI is authoritative. The supported legacy workers.dev origin remains functional. Account/prepaid identities share balances across hosts; preserve the original origin for signed payments and recovery. Origin compatibility.

Tools and prices

ToolMCP identityRESTUSDC per callCurrent prepaid credits
registerfresh402_registerPOST /v1/registerFreeFree
checkfresh402_checkPOST /v1/check$0.0052
extractfresh402_extractPOST /v2/extract$0.0103
smart difffresh402_smart_diffPOST /v2/smart-diff$0.0154
openapi contract difffresh402_openapi_contract_diffPOST /v2/openapi-contract-diff$0.0205
contract watchfresh402_contract_watchPOST /v3/contract-watch$0.0104
wallet watchfresh402_wallet_watchPOST /v3/wallet-watch$0.0208
token factsfresh402_token_factsPOST /v3/token-facts$0.0104
website change intelligencefresh402_website_change_intelligencePOST /v4/workflows/website-change-intelligence$0.0052
api compatibility reviewfresh402_api_compatibility_reviewPOST /v4/workflows/api-compatibility-review$0.0104
onchain evidence brieffresh402_onchain_evidence_briefPOST /v4/workflows/onchain-evidence-brief$0.02510
cross domain release evidencefresh402_cross_domain_release_evidencePOST /v4/workflows/cross-domain-release-evidence$0.04016

New Starter and Developer purchases use the canonical All-Services v4 catalog and cover the seven primitives and eligible tariff-5 workflows after explicit terms acceptance and finalized funding. Historical Web packages retain their accepted scope and original recovery identities. Native USDC on Base 8453 (existing Safe) or Solana Mainnet through x402; native MPP remains Base-only. Network selection, Solana ownership and recovery. Choose explicitly authorized x402 v2, native MPP, or prepaid. Starter $2.50 / 1,000 credits, Developer $15 / 10,000 credits; one-time purchases, not subscriptions, purchased credits do not expire. Pricing and eligibility · Live plans · Account.

After uncertain delivery, recover the original input, operation key and payment evidence; do not authorize a replacement solely because of a timeout. No seed phrase/private key disclosure or unlimited token approval is required. Payment recovery · Agent purchasing.

Source SDK and documentation

The compiled prerelease fresh402-sdk@0.6.1-rc.1 is published under MIT for the public client SDK only. Install explicitly with npm install fresh402-sdk@0.6.1-rc.1 or select @next; latest remains 0.4.0-rc.1. Version 0.5.0-rc.1 adds four server workflow bindings, exact tariff-5 quotes and original-operation recovery alongside seven-service prepaid execution. Node 24+, ESM, declarations, zero runtime dependencies; no automatic wallet/signing or spending. The separately versioned source-client compatibility version remains 0.3.6. Package guide.

Documentation index · API · MCP · Examples · Version relationships · Changelog · Website.

Public HTTPS only: no browser JavaScript execution, authenticated crawling, automatic monitoring scheduler, universal compatibility proof or token safety guarantee. Externally sourced content is untrusted data. Security. The website demo is illustrative and sends no API request.

The existing Registry identity remains io.github.kirillradchenko96/fresh402. Current distribution references. Historical application tags/branches remain accessible; they are not current production deployment instructions. Repository and history boundary.

Support and billing: fresh402@proton.me · Terms · Privacy.

Executable evidence workflows

Four runnable workflows cover website changes, JSON OpenAPI review, finalized Base evidence and cross-domain release observations. Each operation needs explicit authorization and original-operation persistence. Website/API workflow integration is accepted using actual local workerd/D1 with synthetic payments; on-chain orchestration uses the real domain engine with provider fixtures. Individual production canary calls are separate evidence, not a paid end-to-end workflow.

Measured coding-agent value

In three paired GPT-6.1 Sol Website cases, the server workflow achieved 30.9% lower paired-median two-task total cost against building the scoped pipeline, using model API-price equivalents plus Developer consumed-credit fees. Two of three individual pairs were cheaper. Server sessions needed zero project writes; the coding baseline median was two. Exploratory GPT-6 Astra Website and API cases showed 45.1% and 42.9% savings respectively, with one case per condition, not replicated guarantees. Task and model matter; these are controlled evaluations, not organic customer testimonials. Method and complete data.

One task, one server workflow

Four server-executed workflows complement the seven original paid primitives: Website Change Intelligence ($0.005 /2 eligible credits), API Compatibility Review ($0.010 /4), On-chain Evidence Brief ($0.025 /10) and Cross-domain Release Evidence ($0.040 /16). Each has one financial parent and no internal extra charges. New source identities seed in the same charged operation; later owned observations support compact evidence and exact original-result recovery. Finite capacity applies; Base wallet coverage remains a selected-block pilot, and static documents do not prove deployed behavior or causation. No browser rendering or server-side LLM inference.

Live discovery determines availability. Eligible prepaid workflows use exact authenticated tariff-5 quotes and existing constituent rights; purchased package/funding terms and the original seven prices remain unchanged. Use the exact published SDK version listed above; verify npm version and integrity before installation. The older client-orchestrated runFlagship is still distinct and bills its underlying operations separately.

Agent framework integrations: tested MCP connectivity for OpenAI Agents, LangChain/LangGraph, CrewAI and Vercel. Payment authority is separate. Explicit CI contracts and typed Extract projection use existing prices and bounded execution.

Bounded structured evidence: repeated static HTML/JSON records, Release Guardian CI findings, explicit JSON record identity and private caller-retained Website/API context. Existing tools and prices; no browser or automatic payment.

No installation packages available.

Remote