MCP live • EDGAR verified • SPECTRA • signed grants • x402 • OpenAPI 48 paths

Delta SignalATLAS-7

Filing-backed issuer intelligence for the crypto-exposed public-company universe. Daily EDGAR CompanyFacts -> ATLAS-7 evidence rows -> SPECTRA field maps -> REST, MCP, Arazzo, signed grant-session access, and x402 workflows.

What it isEvidence pipeline for 215 crypto-exposed issuers grounded in SEC/XBRL facts.
How it updatesNightly EDGAR waits for CompanyFacts, mirrors or reconstructs the date, then runs process-changes.
What ATLAS-7 addsDaily changes, issuer history, stress, peers, alpha, readiness, caveats, and MCP manifests.
How to integrateDiscover through OpenAPI, /v1/pricing, and /v1/contract/fields; use signed grant sessions or x402 for execution.
Best first probesRead llms-full.txt, then check pricing, field contract, readiness, and MCP discovery before any paid or grant-covered call.

MCP live • EDGAR daily background task verified • OpenAPI 48 paths • /v1/pricing + /v1/contract/fields live • signed grant-session flow live • x402 enabled

Hero visual: SEC/XBRL evidence base -> ATLAS-7 intelligence engine -> agent-ready outputs.

ATLAS-7 Evidence Pipeline diagram showing SEC/XBRL evidence, ATLAS-7 intelligence, agent-ready outputs, access rails, and validation layers
ATLAS-7 generation path: SEC/XBRL evidence -> deterministic intelligence engine -> MCP, REST, Arazzo, signed grant sessions, and x402 outputs.

From filings to usable issuer intelligence

Start with bounded workflows that return structured evidence or readable Markdown, not generic market chatter.

Morning BriefDaily operating picture: readiness status, latest daily changes, risk distribution, top stressed issuers, alpha opportunities, source dates, and caveats.
Company ReportTicker-level diligence: SEC / XBRL fundamentals, covenant stress, peer ranking, alpha signals, source metadata, and quality flags.
Pressure BoardMarket stress view: top stressed names, risk tiers, watchlist pressure, stress caveats, and drilldown targets.
Alpha SweepResearch-candidate screen: alpha opportunity scores, signal pressure, universe-level screen, evidence boundaries, and next drilldown prompts.
SPECTRA Field MapsRuntime ATLAS-history field maps for the 215-row covered universe. Static contracts are fallback only; current SPECTRA maps preserve source date, lineage, caveats, and non-advice boundaries.

Start here: readiness -> Morning Brief -> metadata

New users should get one successful evidence response before choosing REST, MCP, Arazzo, Glama, or x402 details.

Step 1

Read the agent brief

Start with the plain-text operator brief. It gives the exact read order, first probes, trust order, signed grant-session flow, pricing source of truth, parser contract, and billing assumptions agents are allowed to make.

Open llms-full.txt

Step 2

Check system readiness

Use readiness through x402, an active grant, or a payment proof to confirm the active data slice, service health, and payment state. Grant paths include issued identity headers such as X-Codex-User and the wallet grant-session flow: GET /v1/grant/challenge, sign the returned message, POST /v1/grant/session, then attach X-DeltaSignal-Grant-Token. A plain unauthenticated request may correctly return HTTP 402.

GET /v1/readiness

Step 3

Run a bounded scan

Start with a composite or Natural Language route: Morning Brief, Top-Stressed Brief, Pressure Board, or Alpha Sweep.

Starter prompt: Give me a Delta Signal morning brief.

Step 4

Inspect evidence metadata

Check source dates, caveats, quality flags, evidence hashes, renderer status, and non-advice disclaimers before using the result.

Read response metadata guide

Agent read orderFor IDEs and autonomous clients, fetch llms-full.txt first, then changelog-llm.html, then openapi.json, then /v1/pricing, then /v1/contract/fields. That order cuts down drift and prevents stale parser, grant, or pricing assumptions.
Live contract snapshotPublic verification currently shows OpenAPI with 48 paths, live /v1/pricing, live /v1/contract/fields, /v1/grants/status for callers with a resolved grant identity or active grant token, grant-window expiry fields when applicable, Company Report at 0.6 cost_usd, and a signed wallet-grant challenge/session flow.
Billing ruleTreat /v1/pricing as the quote source and the response billing envelope as Delta Signal billing metadata. For plain x402 calls, reconcile actual spend from settlement or payment proof when the wallet moves.
HUT evidence readinessHUT company-report and SPECTRA field-map routes are live behind public x402 challenges. Agent-facing envelopes document issuer_evidence_envelope, evidence_sections, spectra_metadata, and publication_audit_block.
Universe route safetyNo-ticker universe routes reject extra path segments such as /UNIVERSE with structured invalid_path_scope, billing_behavior=not_charged, and cost_usd=0.
Current hardening checkpointRecent integration pressure tests tightened pricing discovery, parser-field stability, compact evidence handling, large-payload guardrails, and grant-session contract wording. Public docs now track the live surface, including explicit budget-grant runway fields when production exposes them, not undeployed source expectations.
Readiness should showService state, active source date, issuer count, live-price status, audit freshness, and route/payment readiness.
Morning Brief should showReadiness, daily changes, risk distribution, top stressed issuers, alpha opportunities, caveats, and a non-advice boundary.
Metadata should showSource dates, computed times, stale flags, quality flags, evidence hashes where available, payload mode, and elapsed time.
Then choose integrationUse REST for direct HTTP, MCP for agents, Arazzo for workflow planning, Glama for connector install, or x402 for grant-covered and paid public access.

Built on SEC / XBRL evidence, not token noise

Delta Signal focuses on public companies exposed to crypto markets. It connects filings, fundamentals, financial pressure, peer context, and daily evidence changes into agent-readable intelligence.

Issuer-level, not token-levelTrack public companies with crypto exposure instead of relying on generic market sentiment.
Daily EDGAR background taskThe MCP evidence base starts with the nightly EDGAR CompanyFacts mirror, readiness wait, process-changes run, delta summaries, intelligence artifacts, and manifest audit.
Filing-backed fundamentalsUse SEC / XBRL company facts as the evidence base for fundamentals and issuer context.
Stress and peer contextCompare covenant stress, risk tiers, and relative position across crypto-exposed public-company groups.
Evidence-preserving outputCompile structured evidence into Markdown while preserving source dates, caveats, quality flags, and disclaimers.
Agent-native accessUse MCP, REST, Open API, Arazzo workflows, or x402-compatible public clients.
Readiness and daily changesMonitor service health, active data slice, changed companies, changed facts, and evidence references.

Live-loop hardening now documented

Recent integration pressure tests tightened the production contract for grants, pricing, field stability, MCP composites, large payloads, notification delivery, and soft-miss semantics.

Dedicated grant pathEnrolled wallet-grant users should use the challenge/session flow: GET /v1/grant/challenge, EIP-191 personal_sign, POST /v1/grant/session, then attach X-DeltaSignal-Grant-Token. Raw unsigned wallet headers are not a grant identity. The signed token is the auth artifact; runway and debit semantics come from the live grant-status and billing fields.
Billing envelopecost_usd is the customer-visible charged-cost field and should stay 0 for grant, API-key, internal, or discovery bypasses. Public grant and x402 envelopes may also expose quoted_cost_usd, actual_cost_usd, credits_charged, billing_mode, payment_status, billing_status, and request_id; reconcile actual x402 spend from settlement or payment proof when the wallet moves.
Pricing discoveryUse /v1/pricing as the live route-pricing source of truth and /v1/contract/fields for canonical response-field semantics. Company Report is no longer the older $0.30 display price; the corrected standard display price is $0.60 with a route-declared range of $0.45-$0.75.
Universe route invariant/v1/readiness, /v1/daily-changes/latest, /v1/alpha-opportunities, /v1/top-stressed, and /v1/risk-distribution are universe-scoped routes and should remain path-ticker-free.
MCP composites exposedMCP clients should discover composite tools before execution and prefer bounded presets such as Morning Brief, Company Report, Pressure Board, Alpha Sweep, and Quick Ticker Check when they match the user intent.
SPECTRA soft missesA structured not_found means no evidence is currently available for that endpoint/ticker pair, not a system failure. Clients can suppress known soft misses briefly and re-probe on a cadence because coverage can be backfilled later.
Large payload noteFor large endpoints such as Company Report, ATLAS history, and Daily Changes, AgentCash/Node integrations should write or redirect output to a file before parsing instead of piping through a short-lived Node process that may truncate stdout around 64 KB.
No-polling notificationsThe notification substrate includes free event discovery, email and terminal delivery, signed webhooks, delivery receipts, retry/dead-letter handling, subscriptions, and paid MCP notification summaries for agent-readable interpretation.

These improvements are public integration guidance. Private design-partner names, mailboxes, wallet addresses, grant balances, and support artifacts are intentionally excluded from this page.

Evidence-preserving outputs

Evidence first. Briefs second. No unsupported invention.

Natural Language route boundary Natural Language briefs render returned Delta Signal evidence into readable Markdown. They do not create new evidence, fill missing data, override source caveats, convert screens into recommendations, or produce personalized investment advice.
Source contextSource dates, filing dates where available, freshness indicators, and stale flags.
Evidence qualityCaveats, quality flags, evidence hashes, renderer status, and route or tool provenance.
Review boundaryBriefs compile returned evidence, preserve metadata, surface caveats, and keep non-advice disclaimers visible.
Missing dataIf evidence is missing, it remains missing and must be surfaced as a caveat.

From filings to agent output

Delta Signal is an evidence pipeline first: SEC / XBRL facts flow into ATLAS-7, then out through REST, MCP, Arazzo workflows, x402 public access, and response metadata.

EDGAR daily task Nightly CompanyFacts readiness, Azure mirror/reconstruction, process-changes, delta summaries, intelligence artifacts, and manifests provide the MCP evidence base.
SEC / XBRL filings Issuer fundamentals, changed facts, filing dates, and source evidence enter the ATLAS-7 pipeline.
ATLAS-7 surfaces Risk, fundamentals, covenant stress, peer ranking, alpha, daily changes, and readiness are exposed as bounded operations.
Agent outputs Clients receive JSON evidence or Markdown briefs with source dates, caveats, quality flags, hashes, and non-advice disclaimers.
EDGAR daily background task -> SEC / XBRL CompanyFacts mirror and reconstruction -> ATLAS-7 issuer pipeline -> risk, fundamentals, stress, peer, alpha, and daily-change surfaces -> REST / MCP / composite presets -> JSON evidence or Markdown briefs -> source dates, caveats, quality flags, hashes, and non-advice disclaimers

How ATLAS-7 and SPECTRA are generated

ATLAS-7 is the issuer evidence layer. SPECTRA is the field-map layer derived from ATLAS history for inspection, comparison, and agent-safe explanation.

ATLAS-7 generationThe daily EDGAR task mirrors or reconstructs CompanyFacts, runs process-changes, matches the crypto-exposed public-company universe, normalizes ticker/CIK identity, and emits dated issuer evidence.
ATLAS-7 outputsThe pipeline writes daily changes, per-CIK change blobs, digital-asset intelligence, calculation history, point-in-time history, readiness, caveats, and manifests that MCP tools can cite.
SPECTRA generationSPECTRA reads ATLAS-history-shaped rows for a ticker, resolves the active source date, normalizes numeric/date/boolean fields, derives pressure and range labels, and packages a field-map contract.
SPECTRA outputsField-map contracts expose what the issuer evidence contains, where values came from, which date bounds apply, and which caveats or soft-miss states prevent overclaiming.
Agent boundaryAgents may explain returned ATLAS-7 and SPECTRA evidence, but they must not invent missing facts, fill unavailable rows, or turn diligence signals into investment advice.
Public routesUse /v1/atlas-history/{ticker}, /v1/point-in-time-history/{ticker}, and /v1/spectra-field-map/{ticker} when a workflow needs the generated history or field-map contract.
EDGAR CompanyFacts + daily feed + full-index -> CompanyFacts mirror or daily-feed reconstruction -> process-changes delta and intelligence artifacts -> ATLAS-7 issuer rows, history, risk, stress, alpha, peer, and daily-change evidence -> SPECTRA field-map contracts derived from ATLAS-history rows -> MCP/REST responses with source dates, caveats, quality flags, and non-advice boundaries

How agents know and run the workflows

MCP clients discover tools, read the Arazzo scenario plan, use OpenAPI for exact routes, and let Coinbase x402 handle public pay-and-retry execution.

Agent workflow runner Codex, Claude Code, and other MCP clients can move from plain intent to a bounded Delta Signal workflow without guessing endpoint order.
MCP + Arazzo + x402

1. Discover

The agent sees the service contract through public metadata and tool discovery.

MCP tools/list /openapi.json /arazzo YAML + JSON /.well-known/x402

2. Plan

Arazzo maps user intent to the right scenario pipeline and required inputs.

marketReadinessScan singleIssuerDiligence dailyMonitoringEvidenceDrilldown mcpCompositePresetSelection

3. Execute

The client calls one MCP composite or follows the REST sequence step by step.

@DeltaSignal morning_brief @DeltaSignal company_report ticker:RIOT GET /v1/readiness GET /v1/daily-change-evidence

4. Resolve

Public clients pay when challenged, retry, then receive structured evidence or a compiled brief.

free metadata discovery 402 on tools/call Base USDC via Coinbase x402 retry with payment proof JSON + Markdown evidence
Access layer publicMcpX402Handshake proves free public tool discovery and the paid tools/call challenge. internalMcpToolSmoke stays for first-party validation.
Analytical REST layer Market scans, issuer diligence, and evidence drilldowns expose exact OpenAPI-backed operations for agent-controlled runs.
MCP composite layer Priced presets such as morning_brief and company_report bundle common sequences into one bounded server-side call.

Seven Arazzo-defined agent workflows

These are the machine-readable scenarios agents can inspect before choosing a tool or route sequence.

publicMcpX402HandshakePOST /mcp allows free tools/list discovery, then returns 402 on unpaid tools/call so x402-capable public clients can pay and retry.
internalMcpToolSmokeFirst-party keyed validation on the same /mcp endpoint. Not public install guidance.
atlas7AuditStatusCheckOperator workflow for the Azure-native 215-row audit status: freshness, artifact prefix, current failures, historical failures, and composite failures.
marketReadinessScanReadiness, risk distribution, top stressed, and alpha opportunities for market-wide triage.
singleIssuerDiligenceFundamentals, alpha signals, covenant stress, peer ranking, and optional ATLAS history for one ticker.
dailyMonitoringEvidenceDrilldownCompact daily changes first, then raw issuer evidence only when explicitly requested.
mcpCompositePresetSelectionUse morning_brief, company_report, pressure_board, alpha_sweep, or quick_ticker_check for bounded server-side workflows.
Open Arazzo YAML Open Arazzo JSON Open x402 Handshake

Canonical agent traces

Concrete examples for how an agent moves from intent to bounded workflow, execution, returned evidence, and renderer rules.

Trace A: Morning BriefIntent: "Give me a Delta Signal morning brief." Execute the Morning Brief composite or Natural Language route. Return readiness, daily changes, risk distribution, top stressed issuers, alpha opportunities, caveats, and metadata. Preserve source dates, quality flags, hashes, renderer status, and non-advice disclaimers.
Trace B: Company ReportIntent: "Run a Delta Signal company report for RIOT." Required input: ticker. Execute Company Report or single-issuer diligence. Return fundamentals, covenant stress, peer ranking, alpha signals, and source metadata. Do not substitute a default ticker; missing evidence remains missing.
Trace C: Pressure BoardIntent: "Show me the current pressure board." Execute the pressure-board composite or bounded market scan. Return top stressed issuers, stress tiers, risk distribution, market-wide pressure context, caveats, and quality flags. Treat the board as triage evidence, not recommendations.
Trace D: Daily Change DrilldownIntent: "Show what changed for ARKB." Start with compact daily changes. Fetch raw issuer evidence only when explicitly requested. Return changed facts, source references, filing metadata, caveats, and hashes.

Pricing for first workflows

Start with free discovery and first calls where a grant or free-tier policy applies. Paid public usage is route-level, usage-based, and declared in live route metadata. Check /v1/pricing first, then confirm with the route-specific x402 challenge when needed.

Design partner feedback and ownership boundary Delta Signal welcomes non-confidential feedback from design partners, early users, integrators, and customers on route contracts, field naming, pricing metadata, response schemas, output limits, and agent-facing documentation. Unless otherwise agreed in writing, that feedback may be used, modified, incorporated, published, or commercialized by Delta Signal without compensation, royalty, attribution requirement, or ownership claim by the contributor. Please do not send confidential code, trading rules, customer data, wallet secrets, API keys, regulated data, or third-party restricted material unless covered by a separate written agreement. Read the public terms.
Morning Brief$0.18. Default daily market scan: readiness, daily changes, risk distribution, top stressed issuers, and alpha opportunities.
Company Report$0.60 standard display price, with a live route-declared range of $0.45-$0.75. Full single-issuer diligence across SEC / XBRL fundamentals, covenant stress, peer ranking, alpha signals, source metadata, quality flags, and live ATLAS-history / SPECTRA when available. Confirm the final route-declared charge through /v1/pricing, OpenAPI metadata, or the x402 challenge before execution.
Pressure Board$0.14. Market stress view with top stressed issuers and risk distribution.
Alpha Sweep$0.14. Opportunity screen with alpha opportunities and daily changes.
Quick Ticker Check$0.18. Fast issuer triage using readiness, covenant stress, and alpha signals.
Natural Language Briefs$0.95 for live top-stressed and morning-brief Markdown routes. Higher-cost planned issuer briefs are priced separately when live.
Finished Morning Brief PDF$4.50 via StrategiX Visual MCP. Workflow: strategix_delta_brief_pdf_full. Produces one polished, branded, auditable PDF per market day from DeltaSignal evidence.
Monthly PDF Subscription$79 for 22 daily briefs with auto-delivery and archive access. Finished artifact pricing is separate from raw DeltaSignal MCP/REST data calls.
Heavy / Multi-Issuer Deep Brief$9.00 for extra issuer drilldowns packaged into a deeper StrategiX-rendered report.
DiscoveryFree metadata and tool inspection: MCP discovery, OpenAPI route inspection, Arazzo workflow metadata, and readiness probes where a grant or policy applies.
Granular readsTypical public reads run about $0.03-$0.10 depending on route: daily changes, readiness, risk distribution, top-stressed, peer ranking, alpha signals, covenant stress, SPECTRA, and issuer detail.
Payment railCompatible public clients use Base USDC via x402 on /v1/*. Tempo/MPP clients use the matching /mpp/v1/* route family.

Live route metadata is the source of truth. Use /v1/pricing for current cost discovery, then reconcile actual x402 spend from settlement or payment proof when the wallet moves.

Start free. Pay only when a route requires it.

Delta Signal supports free discovery, grant-covered access, and route-level paid access through x402-compatible clients.

Free DiscoveryInspect before you spend: service discovery, MCP tool listing, OpenAPI route inspection, readiness probe, and workflow metadata. Route execution may require x402 payment proof or an active grant.
Grant SessionsGrant-covered calls can use issued identity headers or the wallet grant-session flow for enrolled EVM wallets: GET /v1/grant/challenge -> personal_sign -> POST /v1/grant/session -> attach X-DeltaSignal-Grant-Token. Raw unsigned wallet headers do not unlock grants. Use /v1/grants/status with a resolved identity or active grant token to read the active grant model and runway, including grant_expires_at when exposed.
Route-Level PricingEach paid route declares its own cost. Read /v1/pricing before execution; for example, live Company Report pricing is currently 0.6 cost_usd.
x402 Challenge and RetryWhen a paid public route requires payment, the server returns an x402 challenge. Compatible clients settle through Base USDC and retry with payment proof.
Grant Debit SemanticsBudget grants currently debit by route_declared_price. The live contract also reports grant_cache_treatment=fresh_and_cached_charge_same_route_quote for the verified budget-grant path, so fresh and cached covered reads consume the same route quote unless production changes.
Runway fieldsDo not infer grant runway from legacy credit language when explicit fields exist. When production exposes grant_limit_type=budget_usd, grant_limit_unit=usd, grant_budget_usd, or grant_remaining_usd, treat the grant as a USD budget and size usage from those fields. When it exposes grant_expires_at or grant_expires_in_seconds, treat those as the grant-window fields; the plain challenge/session expires_at fields are short TTLs. If those fields are absent, fall back to best-effort grant coverage plus x402.
What You ReceivePaid output still preserves source dates, route metadata, caveats, quality flags, evidence references or hashes where available, and the non-advice boundary.
Simple x402 flow 1. Discover the route. 2. Make the request. 3. Receive x402 challenge if payment is required. 4. Client pays through a compatible x402 flow. 5. Client retries with proof. 6. Delta Signal returns JSON or evidence-preserving Markdown.

Use free discovery and one grant-aware or x402-aware test call before running paid workflows. Start with /v1/pricing, /v1/contract/fields, or a bounded Morning Brief.

Built for agent-native financial intelligence

Delta Signal combines filing-backed issuer data with modern agent infrastructure: MCP discovery, OpenAPI contracts, Arazzo workflows, composite presets, and x402-compatible public access.

SEC / XBRL Evidence BaseGrounded in issuer filings, not social noise. Supports fundamentals, daily evidence changes, issuer-level drilldowns, filing-backed context, and source-date preservation.
Open API PublishedDevelopers can inspect routes, parameters, response shapes, and route families for REST integration, SDK generation, route validation, and schema inspection.
MCP LiveMCP-compatible clients can discover tools and run bounded workflows through the remote MCP endpoint, including composite presets and granular tool calls.
Arazzo WorkflowsMachine-readable scenarios help agents map user intent to market scans, issuer diligence, daily evidence drilldowns, audit checks, and composite preset selection.
Evidence-Preserving MarkdownNatural Language routes compile structured evidence into Markdown while preserving source dates, caveats, quality flags, evidence hashes where available, and non-advice disclaimers.
x402 Public AccessPublic clients can discover, challenge, pay, retry, and receive structured evidence without manual account setup when route metadata requires payment.
Glama VerifiedThe verified Glama connector gives external users another way to discover and validate Delta Signal as an MCP-accessible service.

Delta Signal is designed to be useful on the first request and inspectable before deeper integration. Run Morning Brief or open developer docs.

Natural Language brief routes

Readable evidence packages, not unconstrained opinions. Natural Language routes compile returned Delta Signal evidence into validated Markdown briefs.

Natural Language briefs Raw and composite routes return structured evidence. Natural Language routes compile that evidence into validated Markdown while preserving source dates, caveats, quality flags, evidence hashes, and non-advice disclaimers. They do not create new evidence; they render returned Delta Signal evidence into readable Markdown.
top_stressed_naturalLive. $0.95. Evidence-preserving Markdown brief for highest-stress issuers.
morning_brief_naturalLive. $0.95. Backend-composed Natural Language Morning Brief.
covenant_stress_naturalPlanned. $1.20. Ticker-specific covenant evidence brief.
roadmapAdditional planned briefs include peer ranking, alpha signals, company fundamentals, risk distribution, and daily changes. See Quickstart for the route matrix.

Granular tools for exact control

Use these after you know which workflow, issuer, or evidence layer you want to inspect.

@DeltaSignal readiness @DeltaSignal alpha_signals ticker:COIN @DeltaSignal covenant_stress ticker:MARA @DeltaSignal peer_ranking ticker:COIN @DeltaSignal company_fundamentals ticker:MSTR @DeltaSignal top_stressed tickers:MARA,RIOT,HUT,CLSK @DeltaSignal risk_distribution tickers:COIN,MSTR,MARA,RIOT @DeltaSignal daily_changes @DeltaSignal daily_change_evidence ticker:ARKB limit:100 # TripCode / River tools are discoverable, gated, and evidence-dependent. # Only call them if live MCP tools/list exposes them.
readinessCheck whether Delta Signal is live and which data slice is active.
alpha_signalsIdentify positive or negative signal pressure for one issuer.
covenant_stressInspect debt covenant and financial stress evidence for one issuer.
top_stressedRank the highest-stress crypto public companies.
peer_rankingCompare one issuer against its peer group.
risk_distributionSummarize risk spread across a watchlist.
company_fundamentalsRetrieve SEC XBRL-backed fundamentals.
daily_changesCompact Daily Monitoring: freshness, counts, changed-company rows, and evidence refs. Typical public route price: $0.03.
daily_change_evidenceRetrieve issuer-level proof for changed XBRL tags and source-date evidence.

TripCode research continuity

TripCode / River subscriber research is visible in public MCP discovery, but execution is x402/grant-gated and evidence-dependent. Subscribers can paste a TripCode into Codex or Claude Code only when the live tool call can resolve the required River / issuer index blobs.

TF-SUBArticle and narrative research nodes. Generated from DeltaSignal research identity, not Substack post ID. Resolve price: $0.02.
TF-XBRLSEC/XBRL evidence nodes. Preserves accession, CIK, form, period, source documents, and caveats. Resolve price: $0.02.
TF-DSComputed DeltaSignal signal nodes for future resolver expansion: alpha, stress, SPECTRA, peer, and readiness outputs.
TF-RIVERIssuer thesis Rivers group prior TF-SUB article nodes, TF-XBRL evidence, TF-DS signals, claim lineage, and monitoring checkpoints. Resolve price: $0.05. Reverse search: $0.30.
CompareArticle-to-filing verification returns confirmed signals, weakened assumptions, execution bridge risks, proof milestones, and monitor items. Price: $0.08.
Thesis MapOne-call subscriber output with what changed, confirmed signals, weakened assumptions, bridge risks, 2027 proof milestones, scenario map, invalidation rules, and monitors. Price: $0.30.
AuthoringGenerate article and filing TripCodes for deterministic authoring metadata. Price: $0.00 for generation tools.
MCP/x402 Subscriber FlowDiscovery is free. Paid tools/call uses grant, free-tier allowance, or x402 payment and retry. Full paid article content is entitlement-gated.
Subscriber prompt Use DeltaSignal MCP. Load article TripCode TF-SUB-XXXXXXXXXX. Discover prior TF-SUB article nodes in the issuer River. Reverse-search the River for thesis deltas and claim lineage. Build the article thesis map from the current article and discovered River continuity. If an x402 challenge is returned, use a compatible x402 client or grant and retry. Return missing or restricted content explicitly. Do not invent facts.

Build a GET route

Natural Language GET routes use query parameters, not JSON request bodies.

https://api.aitrailblazer.net/v1/top-stressed/natural?limit=10&style=professional

Install in your agent client

Install details come after the first-test and pricing model so you know which path you are enabling.

Coinbase + Codex npx @coinbase/payments-mcp install codex plugin marketplace add aitrailblazer/deltasignal-atlas-codex-plugin Coinbase + Claude Code npx @coinbase/payments-mcp install --client claude-code claude mcp add --transport http deltasignal-atlas-7 https://api.aitrailblazer.net/mcp REST only Open https://api.aitrailblazer.net/openapi.json and call the route family directly.

Reference surfaces

Inspect the exact contracts when you need implementation detail: schemas, pricing, parser fields, workflows, MCP endpoint, x402 handshake, and agent-readable guidance.

Coinbase x402 / Codex marketplace review path

Review Delta Signal as a paid evidence API for Codex workflows: install, discover, inspect route metadata, use grant-session or x402 challenge flow, retry with proof or token, and verify returned provenance before trusting rendered prose.

Reviewer lifecycle

Start with free discovery, then verify the challenge/retry path before running paid workflows.

MCP tools/list
OpenAPI
402 challenge
paid retry

Bazaar discovery proof

Pass requires extensions.bazaar.routeTemplate=/v1/readiness, an output example, merchant resources for the seller payTo, and no Agentic Market first-party verification claim until the UI or Coinbase team confirms it.

payTo
merchant resources
Bazaar metadata
validated
Readiness routeRecommended first reviewer test; returns current service state or a valid public payment challenge.
MCP discoveryWorks before paid calls so agents can inspect available tools.
OpenAPI contractShows reachable public routes, route metadata, and 402 response shape.
x402 challengeReturns expected network, asset, seller, and amount metadata before retry. Public clients should reconcile actual spend from settlement or payment proof.
Paid retryReturns structured JSON or Markdown evidence after compatible payment proof.
Response metadataIncludes source dates, caveats, quality flags, and non-advice boundaries.
Review targetValidate ATLAS-7 x402 issuer intelligence first: Morning Brief, Company Report, Pressure Board, Alpha Sweep, Quick Ticker Check, and issuer drilldowns.
TripCode caveatTripCode/River subscriber research is discoverable in public MCP, but execution is x402/grant-gated and depends on required River/index blobs being available.

Verified developer surfaces

Technical buyers can validate the public MCP endpoint, Open API contract, and x402 payment rail before paid use.

Public MCP + Open API

Agents can inspect the hosted Streamable HTTP MCP endpoint and public route contract, then use signed grant-session access or x402 routes under /v1/* for execution.

Agent client
/mcp
ATLAS-7 tools
JSON result

x402 / Bazaar Settlement

When free calls are exhausted, the route returns a 402 challenge with Bazaar metadata and settles paid calls with Base USDC.

402 challenge
Base USDC
verify + settle
paid data

Live versus planned route status

Know what is callable now. Treat route status as operational metadata and confirm the current surface in OpenAPI, Quickstart, or route metadata before wiring production flows.

Live core routesReadiness, top stressed, risk distribution, alpha opportunities, daily changes, and issuer evidence routes where listed in the current OpenAPI surface.
Live Natural Language routestop_stressed_natural, morning_brief_natural, and covenant_stress_natural are evidence-preserving Markdown routes where current route metadata confirms them. They can be grant-covered when the signed-session grant contract includes the exact route, otherwise they fall back to x402/payment-required behavior.
Composite routesMorning Brief, Company Report, Pressure Board, Alpha Sweep, and Quick Ticker Check are the recommended first workflow layer when exposed by MCP/composite metadata.
Planned briefscovenant_stress_natural and additional peer ranking, alpha signals, company fundamentals, risk distribution, and daily changes briefs should be treated as roadmap until current references mark them callable.

Claude Code and agent setup

Use the project guide before running Delta Signal from Claude Code, Codex, or any MCP-compatible coding agent. It keeps the first run bounded and evidence-preserving.

Guide

Open CLAUDE.md

The Claude Code guide explains MCP install commands, readiness checks, composite-first tool use, x402 boundaries, TripCode caveats, and refusal rules.

Read CLAUDE.md

Install

Add the MCP endpoint

Install Coinbase payments support where needed, then add https://api.aitrailblazer.net/mcp as the Delta Signal ATLAS-7 MCP server.

First Run

Discover, then execute

Start with MCP tools/list, check readiness, run one bounded composite, then inspect source dates, caveats, quality flags, payment metadata, and non-advice boundaries.

Boundary

Evidence first

Agents may summarize returned evidence, but they must not invent missing facts, override caveats, turn screens into recommendations, or claim unavailable drilldowns were fetched.

Claude Code MCP install reference npx @coinbase/payments-mcp install --client claude-code claude mcp add --transport http deltasignal-atlas-7 https://api.aitrailblazer.net/mcp # First prompt: # Give me a Delta Signal morning brief, then show source_date, # route_uri, cost_usd, caveats, and non-advice boundary.

Operator and audit workflows

Operational visibility helps confirm whether the ATLAS-7 pipeline is healthy before users depend on live evidence outputs.

atlas7AuditStatusCheckChecks audit freshness, artifact prefix, current failures, historical failures, and composite failures.
Readiness validationConfirms active data slice, freshness, live-price status, issuer count, and service availability.
Source metadata completenessUse response metadata to verify source dates, caveats, quality flags, and evidence references before downstream rendering.
Failure visibilitySurface current, historical, and composite failures as validation context instead of hiding them behind successful route responses.

Developer copy block: first call

Copy, run, inspect. Start with readiness, then run a bounded workflow through your selected access path.

curl https://api.aitrailblazer.net/v1/readiness # A plain public curl may return HTTP 402 with an x402 challenge. # x402-compatible clients should attach payment proof or an active # grant context, then retry the same route. # Then run a bounded workflow through REST, MCP, Glama, # an Arazzo-guided agent sequence, or an x402-compatible public client. # After the response returns, inspect: # source_date, computed_at, stale, caveats, quality_flags, # evidence_hashes, renderer_status, route_price, and payload_mode.

Build with SEC-grounded issuer intelligence

Delta Signal ATLAS-7 turns SEC / XBRL filings for crypto-exposed public companies into structured evidence, bounded workflows, and agent-ready outputs.

For agentsDiscover the service contract, select a bounded workflow, execute through MCP or REST, preserve the returned metadata, and render evidence without inventing unsupported claims.
For developersStart with /v1/pricing, /v1/contract/fields, and readiness through the correct grant or x402 path, then inspect OpenAPI and Arazzo for exact schemas or workflow automation.
For analystsUse Morning Brief, Company Report, Pressure Board, Alpha Sweep, Quick Ticker Check, and Peer Context as research inputs, not recommendations.

Start with readiness through the correct x402/free-tier path. Run one bounded brief. Trust the evidence metadata before the narrative.