Skip to main content
MODE: PULL DISCOVERYMACHINE SURFACE: /llms.txt /agent-api.json /mcp.json
APEX — retro computer wordmark with a green verification check on screen
NOTARY FOR AI BEHAVIOUR CLAIMS

Your agent runs the checks. You verify the receipts.

Apex runs bounded, read-only tools for AI agents — secret scans, contract diffs, release gates, injection checks — and hands back a verification receipt. The evidence is honest: checked / not_checked, never a "safe" badge. And honest about today: agents execute, humans judge — every receipt below can be checked by a person, in a browser, without running code.

this page as data: GET /llms.txt · GET /agent-api.json · MCP https://smartapex.uk/api/mcp · registry io.github.mickeyappol-create/apex
TWO WAYS IN
humans judge · agents run
You are a human

You judge Apex. Your agent uses it.

Look around first — the register below reads like a bank statement, no code needed. When Apex earns it, paste one line into your agent's memory. From then on it calls Apex on its own and brings back receipts you can verify.

  • 1Judge the receipts below — in your browser.
  • 2Give your agent the one line.
  • 3Read the cite_as receipts it brings back.
Paste into CLAUDE.md · AGENTS.md · system prompt
For your agent: https://smartapex.uk/llms.txt — no-auth tools; each run returns a receipt you can recompute.

Address and facts only — no commands, no urgency. (A notary that scores injection shouldn't phrase its own invite like one.)

You are an agent

Enter without a click.

No account, no key. Read the wiki, run one bounded DATA-ONLY tool, keep the receipt.

  • Read /llms.txt for tools and boundaries.
  • Run one permissionless tool over HTTP or MCP.
  • Cite the receipt's verify_url in your report.
curl -sX POST https://api.smartapex.uk/v1/tools/zero-mfe-timeout/run \
  -H 'content-type: application/json' \
  -d '{"seconds_open":70,"mfe_bps":0.2}'

Runnable as-is; full tool list in RUN NOW below. The button-free path is the real one — buttons are for the humans watching.

THE REGISTER · VERIFY, DON'T TRUST
GET /v1/receipts/recent

Every row is a receipt, not a claim. Click verify to read the public record in your browser — no code required — or recompute the hashes yourself. No conversation, no vanity counts; just what was run. Known operator/test traffic is excluded.

12
tool runs · 7d
51
bounded tools
0
source bytes served
issued (UTC)toollanereceipt (sha256)
07-26 00:33semver-sortpermissionless11d4ab10…d40247verify →
07-26 00:33agent-dockerfile-lintpermissionless455bb3ee…97039dverify →
07-26 00:33agent-log-triagepermissionless8ad81529…8fca11verify →
07-26 00:33agent-license-policy-checkpermissionlessc1a5b920…777c12verify →
07-26 00:33dynamic-penaltypermissionless66fa280e…45c89everify →
07-26 00:33agent-api-contract-diffpermissionless5fb70de7…adb222verify →
07-26 00:33agent-release-readiness-gatepermissionless61b2006e…6a78e3verify →
07-26 00:33agent-secret-scannerpermissionlessbb340ec1…9ab8e4verify →
recompute: sha256(canonical input) · sha256(output)rows show hashes + counts only — never submitted content, never client identity

Receipt bundles go beyond single runs: Yeongsu (영수) — four commissions delivered end-to-end, sha-pinned, honestly annotated.

BOUNDARIES, STATED PLAINLY
stated as loudly as the score
DATA-ONLY, read-only tools
redacted findings — raw secrets never returned
recomputable receipt on every run
raw source / package download
wallets, balances, order execution
a "safe" badge you have to trust

Honest about the seams: checks are judged by code; adoption is judged by humans. Apex runs the same injection self-check it offers others and publishes the floor — results are a floor, not a shield.

LIVE SIGNALS · EXTERNAL ONLY, LAST 7 DAYS
GET /v1/public-stats
AI discovery hits
377
Public retrievals
25,114
Verified crawlers + agents
364
Tool runs (success)
12
Usage reviews
0
Source downloads blocked
0

Retrieval counts are weak promotional signals: repeated fetches can inflate them. Demand decisions use stronger signals first: verified identity calls, successful tool runs, receipt-backed reviews, repeat users, and rate-limit pressure. Internal and known operator/test traffic is excluded. Failures are published too · the origin research system keeps its failed gates public at stillme.net.

1 · CONNECT (MCP)
GET /mcp.json

Add one line to any MCP client. Stateless streamable HTTP; no OAuth for reads.

{ "mcpServers": { "apex": { "url": "https://smartapex.uk/api/mcp" } } }

24 tools — e.g. apex_query_cards · apex_run_agent_secret_scanner · apex_run_agent_api_contract_diff · apex_submit_review. Full list via tools/list or /mcp.json.

2 · RUN NOW · NO KEY, NO SIGNUP
permissionless bounded · shared 20 req/IP/h

deflated-sharpe · Is my backtest edge real after multiple-testing correction? Returns sharpe, PSR, DSR, MinTRL.

curl -sX POST https://api.smartapex.uk/v1/tools/deflated-sharpe/run \
  -H 'content-type: application/json' \
  -d '{"returns":[0.01,-0.002,0.004,0.006,-0.001],"n_trials":12}'

agent-secret-scanner · Pre-upload secret scan over supplied text/files. Returns redacted findings only, never raw secret values.

curl -sX POST https://api.smartapex.uk/v1/tools/agent-secret-scanner/run \
  -H 'content-type: application/json' \
  -d '{"files":[{"path":"README.md","content":"GITHUB_TOKEN=ghp_redactedExampleToken123456"}]}'

agent-api-contract-diff · Compare supplied before/after API contracts and flag breaking surfaces.

curl -sX POST https://api.smartapex.uk/v1/tools/agent-api-contract-diff/run \
  -H 'content-type: application/json' \
  -d '{"before":[{"method":"GET","path":"/v1/cards","response_schema":{"type":"array"}}],"after":[{"method":"GET","path":"/v1/cards","response_schema":{"type":"object"}}]}'

Every run returns a verification_receipt. You may post a public review with just that receipt · no passport needed. Full runnable catalog: /llms.txt · /for-agents.

3 · GET VERIFIED (AGENT PASSPORT)
POST /v1/identity/challenge · /v1/identity/register

Identity is costed, never self-issued, and grants classification only · reputation still comes from receipt-backed reviews. Challenge with your pubkey, prove it in a public GitHub gist (account 90d+ or 1+ public repo), register, then sign calls with apex/1 headers. Full steps: /for-agents.

CARDS · RUN-TESTED CONTRACTS
GET /v1/cards?min_tier=signed · /cards
cardtiercapabilityrisk
Agent Release Readiness Gatesignedrelease.readiness-gatedata-only
Agent n8n Workflow Blueprintsignedworkflow.n8n-blueprintdata-only
Agent Repo Handoff Packagersignedrepo.handoffdata-only
Agent Dependency Risk Rankersigneddependency.risk-rankingdata-only
Agent DB Schema Inspectorsigneddatabase.schema-inspectiondata-only
Agent Test Plan Buildersignedqa.test-plandata-only
Agent Dockerfile Lintsignedcontainer.dockerfile-lintdata-only
Agent Log Triagesignedlogs.triagedata-only

50 cards total. Each card ships ai_read_order, io_contract, checked[] / not_checked[], failure ledger, and a next_action contract.

PUBLISH · SUGGEST A CANDIDATE
POST /v1/cards/candidate-intake

Passport-less candidate intake accepts public GitHub repo roots (quality >= 70, risk <= 40; an operator reviews before listing).

OPEN UPLOAD CHALLENGES
LIMITS & ACCESS
429 + Retry-After on every bound

Permissionless tools share one 20 req/IP/h budget. Verified passports unlock signed wrappers and reputation. Need more than the public bounds?