Delta Signal ATLAS-7 • Issuer Intelligence + Synthetic Basket Evidence

Start with the live contract

Use this order for a first integration or review pass. It keeps discovery free, avoids customer API keys, and makes every paid or grant-covered call attributable.

1

Discover

Read /v1/pricing, /v1/contract/fields, OpenAPI, and MCP tools/list before hard-coding route prices, parser fields, or tool names.

2

Choose access

Use x402 challenge/retry for public paid execution. Enrolled wallets can mint signed grant sessions that resolve to backend database-managed grant budgets.

3

Run one workflow

Start with Morning Brief, Alpha Sweep, Pressure Board, Company Report, or Quick Ticker Check, then inspect evidence metadata before trusting any prose.

4

Preserve evidence

Store source dates, quality flags, caveats, evidence hashes, billing state, grant runway fields, and the non-advice boundary with each result.

PricingAuthoritative route costs and grant-debit assumptions.GET /v1/pricing Field ContractParser-stable fields, evidence rules, and response metadata.GET /v1/contract/fields OpenAPILive REST route map, schemas, and x402 response contracts.GET /openapi.json

x402-first public access

Public clients do not need Delta Signal API keys. Use route-level x402 or signed wallet grant sessions, then preserve per-call billing and evidence metadata.

x402 paid callsUnauthenticated protected routes may return HTTP 402. Compatible clients settle through Base USDC and retry with payment proof.

Signed wallet grantsEnrolled wallets use /v1/grant/challenge, sign the message, call /v1/grant/session, then attach X-DeltaSignal-Grant-Token.

Backend grant databaseThe backend maps signed wallets to budget/runway records such as grant_budget_usd, grant_remaining_usd, and grant_expires_at.

Deterministic clientsNode, Go, .NET, cron, and dashboards can call REST directly through x402 or wallet grants without an agent runtime.

Choose a workflow

Composite presets bundle the right evidence routes behind one request, so users do not have to guess endpoint order.

Daily Operating Picture
"Give me a Delta Signal morning brief."
Includes readiness, daily changes, risk distribution, top stressed issuers, and alpha opportunities.

Issuer Diligence
"Run a Delta Signal company report for RIOT."
Includes fundamentals, covenant stress, peer ranking, alpha signals, and source metadata.

Market Pressure Board
"Show me the current pressure board."
Includes top stressed issuers, stress tiers, and risk distribution.

Alpha Sweep
"Run an alpha sweep for the current universe."
Includes alpha opportunities, issuer candidates, caveats, and quality flags.

Quick Ticker Check
"Quick check MARA before I drill into it."
Includes compact issuer snapshot, stress signal, peer context, and next drilldown options.

Synthetic Basket Pressure
"Show the Synthetic AI10 Basket pressure state."
Use for basket pressure, audit caveats, linked-market boundaries, and SPECTRA context.

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.

DeltaSignal Synthetic Basket layer

DeltaSignal Synthetic Baskets are evidence-backed baskets used to explain where issuer truth, public-market behavior, basket pressure, and listed derivative pressure align or diverge. They are not third-party-branded products and they are not personalized investment advice.

DeltaSignal Synthetic AI10 BasketA concentrated AI-leader basket for asking whether filing-backed issuer truth, public-market behavior, basket pressure, and linked derivative evidence confirm each other.

DeltaSignal Synthetic Innovators 100 BasketA broader innovation and technology basket for reading whether pressure is isolated to a few companies or spreading across a wider public-company cohort.

DeltaSignal Synthetic AI Power Infrastructure BasketTracks the physical AI bottleneck: power, grid capacity, data centers, compute infrastructure, and miner-to-HPC transition evidence when issuer truth supports it.

DeltaSignal Synthetic Semiconductor 25 BasketA semiconductor supply-chain pressure lane for AI compute hardware, public-market behavior, and basket-level stress.

Four evidence levelsLevel 1 issuer truth, Level 2 public-market behavior, Level 3 basket pressure, and Level 4 derivative dislocation where a linked venue product exists. Missing levels remain explicit.

Public wording boundaryThe public surface uses DeltaSignal Synthetic Basket names. Source files, weights, hashes, and provider-specific lineage remain internal evidence metadata unless the live route explicitly exposes them.

215 core issuer rowsThe original crypto-exposed public-company universe, with 201 nonblank unique tickers and 13 CIK-only or unresolved ticker rows.

378 current calculation issuersThe July 15 calculation plane covers 215 crypto-canonical issuers plus 163 expanded public-equity issuers. The earlier 312-row / 298-ticker expanded snapshot remains historical context, not the current replay universe.

326 synthetic membership rowsCurrent synthetic basket membership surface across 180 unique public-equity tickers and 2 canonical linked perp instruments.

Crypto-native lanesCrypto industry innovators, bitcoin mining infrastructure, digital asset infrastructure, crypto treasury exposure, AI + power overlap, public market rails, and speculative/emerging crypto issuers.

July 15 calculation-plane and semantic MCP verification

The public contract is synchronized to the final issuer-wide replay and customer-route audit rather than an older coverage snapshot.

378-issuer replayThe CompanyFacts/PIT run completed 378 of 378 issuers and materialized 817,992 point-in-time rows with 0 errors.

215-issuer customer auditThe separate route audit executed 1,935 operations: 1,923 successful, 0 failed, 0 skipped, and 12 explicitly not applicable.

68 REST pathsLive OpenAPI 1.5.2 exposes 68 paths. Pricing currently publishes 30 routes and the parser contract publishes 47 fields.

81 MCP toolsLive public discovery exposes 81 tools, including 26 governed atlas7_* semantic tools.

Semantic query disciplineInspect the model and field catalogs first, compile governed queries when needed, and preserve the evidence envelope. Raw SQL is never returned.

Evidence boundaryThe 378-issuer calculation replay and the 215-issuer customer-route regression audit are different scopes. Do not merge their counts or infer unavailable evidence.

Ask MCP for help first

deltasignal_help is a live, public, no-key, free discovery-tier MCP tool. Use it when a user or agent does not yet know the exact workflow name, input schema, pricing surface, grant behavior, or Synthetic Basket / SPECTRA boundary.

Natural Language front doorAsk "help", "what can I ask?", "help perps", "show examples", "help pricing", or "list workflows" before paid execution.

Free discovery envelopeThe live response returns schema_id=deltasignal.help.v1, payment_status=free_discovery, billing_status=not_charged, and x402_required=false.

Example promptsHelp includes copy-ready prompts for Morning Brief, Company Report, Quick Ticker Check, Pressure Board, Alpha Sweep, Daily Changes, SPECTRA, Synthetic AI10, MCP discovery, pricing, and grants.

Perp boundarytopic=perps explains that Coinbase perp and SPECTRA public reads are over recorded/materialized factor rows, not live exchange fetches, raw order-book ladders, or trade instructions.

curl -sS https://api.aitrailblazer.net/mcp \ -H 'content-type: application/json' \ --data '{"jsonrpc":"2.0","id":"help","method":"tools/call","params":{"name":"deltasignal_help","arguments":{"topic":"overview","detail":"short","include_examples":true}}}'

curl -sS https://api.aitrailblazer.net/mcp \ -H 'content-type: application/json' \ --data '{"jsonrpc":"2.0","id":"help-perps","method":"tools/call","params":{"name":"deltasignal_help","arguments":{"topic":"perps","detail":"short","include_examples":true}}}'

Ask Synthetic AI10 questions in plain English

Delta Signal MCP now exposes Synthetic AI10 as a discoverable workflow, so users do not need to know the raw tool names before asking useful questions.

Start with helpAsk help groups to see available workflow groups, then ask help synthetic ai10 for focused Synthetic AI10 prompts, boundaries, and the right next command.

Current stateAsk: What is the Synthetic AI10 pressure state right now? This should route to the compact pressure-state workflow and preserve source dates, caveats, and quality flags.

Drivers and deltasAsk: What factors are driving the Synthetic AI10 state? Driver questions should route to audit mode because they require current bucket, previous bucket, deltas, factor history, and provenance.

Event confirmationAsk: Is Synthetic AI10 in a confirmed ATLAS-7 release event? The answer must use threshold flags and event classification, not only the visible pressure label.

Audit payloadAsk: Show the Synthetic AI10 audit payload with z-scores, threshold flags, and four-level coverage. This is the right path for technical validation and publication review.

Answer completenessAudit mode now also exposes constituent contribution readiness, presentation parity status, TRIDENT availability, liquidation-gradient availability, and question-readiness guidance for agent answers.

Publish safelyAsk: Can we safely publish this Synthetic AI10 read? The answer should separate live facts, caveats, unresolved validation, and non-advice boundaries.

Compact routeUse deltasignal_synthetic_etf_pressure_state for plain current-state questions such as “what is the state?”

Audit routeUse deltasignal_synthetic_etf_audit for “why,” “what changed,” “is it confirmed,” “do we have z-scores,” “do we have threshold flags,” or “can we publish this?”

Live verificationAzure revision ca-web-intel-mcp--0000577 returned audit_status=complete, source_date=2026-06-30, observed_bucket_utc=2026-07-01T14:45:00Z, and a 656-row audit export for Synthetic AI10.

Certification boundaryThe latest live audit still reports canonical_event_status=not_confirmed. Treat Synthetic AI10 as pressure-state evidence unless threshold and coverage evidence confirm a canonical ATLAS-7 event.

BoundaryDelta Signal Synthetic AI 10 Basket is a synthetic benchmark pressure-state workflow. It is not a regulated ETF claim, not issuer truth by itself, not exchange-native microstructure truth, not a broker signal, and not investment advice.

First live probe details

Use this drilldown after the four-step start path when you need the exact help, readiness, billing, and metadata checks for an agent or deterministic client.

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

Ask MCP for help

Call deltasignal_help through MCP when you need examples, available workflow orientation, pricing/grant guidance, or Synthetic Basket / SPECTRA boundaries before a paid route.

Copy the no-key MCP help command

Step 3

Check system readiness

Use readiness through x402, a signed wallet grant session, or a payment proof to confirm the active data slice, service health, and payment state. Public clients do not need Delta Signal API keys. Grant-covered access uses the wallet grant-session flow: GET /v1/grant/challenge, sign the returned message, POST /v1/grant/session, then attach X-DeltaSignal-Grant-Token. The backend maps enrolled wallets to database-managed grant budgets. A plain unauthenticated request may correctly return HTTP 402.

GET /v1/readiness

Step 4

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 5

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 68 paths, MCP discovery with 81 tools including 26 governed semantic tools, 30 priced routes, 47 parser-contract fields, /v1/grants/status for callers with a resolved grant identity or active grant token, 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. Standard Base x402 is the compatibility-first requirement; Circle Gateway is an explicitly selected additive path for Circle-aware clients. Reconcile paid calls from the response settlement receipt plus settlement or payment proof.

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.

July 15 x402 checkpointProduction revision ca-web-intel-mcp--0000594 restores standard-first compatibility and honors an explicitly selected Circle requirement. A bounded standard readiness call settled for 0.04 USDC; Circle routing reached the Gateway facilitator and failed closed with insufficient_balance because the test wallet had no available Gateway balance.

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, settlement_receipt, and request_id; reconcile actual paid spend from the per-call receipt plus settlement or payment proof.

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.

Use Delta Signal your way

Start with a bounded workflow, then choose the access path that fits your stack: agent clients, deterministic REST clients, workflow-aware agents, or public x402 routes.

Agent Clients Run Delta Signal from Codex, Claude Code, or MCP-compatible clients. Best for agent-native workflows, analyst assistants, coding agents, MCP tool discovery, and quick market or issuer scans. Install MCP connector REST API Call Delta Signal directly from your application through x402 challenge/retry or signed wallet grant sessions. Best for backend integrations, dashboards, internal research tools, custom data pipelines, and route-level control without customer API keys. Open API reference Deterministic Daily Client Use Node, Go, .NET, or cron to pull readiness, alpha opportunities, risk distribution, top stressed issuers, and ticker drilldowns. Store evidence metadata, billing metadata, grant runway fields, caveats, and non-advice boundaries per call. x402-first REST workflow Composite Workflows Use one request for common analyst jobs: Morning Brief, Company Report, Pressure Board, Alpha Sweep, and Quick Ticker Check. Best for predictable outputs, lower client complexity, and faster time to value. Run a composite workflow Workflow-Aware Agents Let agents inspect Arazzo scenario plans before execution. Best for tool routers, workflow validation, scenario-specific execution, and reproducible route planning. View Arazzo workflows Public x402 Routes Use payment-aware public access without API keys. Compatible clients discover the service, receive an x402 challenge, settle through Base USDC, and retry with proof. Enrolled wallets can use signed grant sessions instead of settlement while budget remains. Validate x402 flow

Not sure where to start? Use the composite Morning Brief first through x402 or a signed wallet grant session. Run Morning Brief.

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, readiness, and DeltaSignal Synthetic Basket pressure views 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 -> DeltaSignal Synthetic Basket and pressure layers -> 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.

@DeltaSignal deltasignal_help 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 deltasignal_help gives no-key Natural Language orientation. 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.

deltasignal_helpFree public MCP discovery tool for examples, available workflows, pricing/grant orientation, Synthetic Basket pressure-state guidance, SPECTRA boundaries, and safe next commands.

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. Paid public usage is route-level, usage-based, and declared in live route metadata. Public buyers use x402 challenge/retry. Enrolled design-partner wallets can mint signed grant sessions backed by the Delta Signal grant database. Check /v1/pricing first, then confirm with the route-specific x402 challenge when needed.

Delta Signal pricing applies only to Delta Signal-derived evidence workflows and analytical outputs. It does not provide access to, redistribute, or resell any upstream market-data feed.

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/*: standard at accepts[0], with explicit Circle GatewayWalletBatched selection at accepts[1]. 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. Route prices are for Delta Signal-derived evidence workflows only, not upstream market-data access or redistribution.

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.

Wallet Grant SessionsGrant-covered calls use 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. The backend resolves the signed wallet to database-managed grant budget/runway records. Use /v1/grants/status with an active grant token or resolved wallet identity to read fields such as grant_budget_usd, grant_remaining_usd, and grant_expires_at.

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.

Hedera ProofPay preview

ProofPay adds a separate Hedera testnet x402 path for deterministic DeltaSignal evidence. It does not replace or silently modify the live Base, Circle, grant, or MPP route families.

Deployed backendInspect the public preview at proofpay-hedera.kindbeach-299ce8c4.eastus.azurecontainerapps.io. Health, discovery, catalog, quote creation, and OpenAPI are free.

Exact HBAR challengeCreate a single-use quote, call its paid resource URL, receive HTTP 402 for hedera:testnet HBAR, then let an approved x402 buyer settle and retry.

Payment-to-artifact proofAfter mirror-node verification, ProofPay releases the sealed artifact and signs a receipt binding payment, request, evidence, output, source date, and software commit.

Evidence boundaryThe preview currently uses a deterministic MSTR filing-evidence fixture for the bounty. It is not arbitrary live MCP fulfillment, live market data, or investment advice.

Safe Hedera discovery — no payment PROOFPAY=https://proofpay-hedera.kindbeach-299ce8c4.eastus.azurecontainerapps.io curl -fsSL "$PROOFPAY/.well-known/proofpay" | jq curl -fsSL "$PROOFPAY/catalog" | jq curl -fsSL -X POST "$PROOFPAY/quotes" \ -H 'content-type: application/json' \ -d '{"ticker":"MSTR","period":"2025-12-31"}' | jq

Live ProofPay discoveryNetwork, asset, seller, endpoints, evidence boundary, and performed-payment proof.GET /.well-known/proofpay Open-source verifierHedera x402 client, receipt verifier, tests, proof bundle, demo, and transcript.github.com/aitrailblazer/proofpay-hedera-x402 Performed testnet settlementCompleted payment from value buyer to seller, with facilitator-paid network fee.0.0.7162784-1784665192-906989595

Creating or reading a quote does not move funds. Do not sign or submit a Hedera payment without explicit user approval, and never expose the buyer private key.

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 signed grant-session proof 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.

Glama Use the verified Glama connector for Streamable HTTP MCP access. Open Glama connector REST Quickstart Path Use OpenAPI if you want direct HTTP route control instead of MCP. Open API reference Quickstart Route-level integration, response metadata, fallback modes, and SDK wiring. ./quickstart.md

Reference surfaces

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

Open API 3.1 Public route contract for raw, composite, x402, Natural Language, pricing discovery, semantic, and field-contract discovery surfaces. Current live OpenAPI exposes 68 paths. https://api.aitrailblazer.net/openapi.json Live Pricing Authoritative route cost discovery for public clients, including current cost_usd values and grant-session metadata. https://api.aitrailblazer.net/v1/pricing Field Contract Parser-stable field discovery for response paths you should preserve or key on before you wire an agent parser. https://api.aitrailblazer.net/v1/contract/fields Changelog Public changelog for atomic Company Report routes, OpenAPI discovery, ATLAS-7 history, audit status, SPECTRA, x402, and MCP workflow upgrades. ./changelog.html LLM Changelog LLM-optimized changelog with instructions, tripcodes, breadcrumb bread, and an ordered tracking river. ./changelog-llm.html Quickstart Route-level integration, response metadata, fallback modes, and SDK wiring. ./quickstart.md LLM Instructions Agent-facing rules for evidence boundaries, renderer metadata, and non-advice constraints. ./llms.txt Full Agent Brief Canonical operator contract for IDE agents: exact read order, first probes, grant sizing rules, billing and reconciliation rules, parser guidance, MCP call shape, and production boundaries. ./llms-full.txt Claude Code Guide Project-level Claude Code instructions for MCP install, readiness, composite-first tool use, x402 payment boundaries, refusal rules, and HUT TripCode caveats. ./CLAUDE.md Arazzo YAML Machine-readable workflow plans for agents. ./arazzo/deltasignal-arazzo.yaml Arazzo JSON JSON mirror of the workflow plan for clients that prefer JSON. ./arazzo/deltasignal-arazzo.json x402 Handshake Public payment challenge and retry workflow. ./arazzo/publicMcpX402Handshake.arazzo.yaml

Circle Agent Marketplace review path

Review Delta Signal as an x402-compatible seller service for AI agents: discover the public contract, verify standard Base x402 at accepts[0] and Circle Gateway at accepts[1], retry through the selected capability or a grant token, and preserve returned evidence provenance.

Seller service lifecycle

Start with free discovery, then verify the 402 challenge, Circle-aware payment option, paid retry, and per-call receipt metadata before listing.

MCP tools/list

OpenAPI

402 challenge

receipt

Circle-ready payment proof

Pass requires a public x402 resource, seller payTo, amount, network, asset, standard Base x402 compatibility, and an explicitly selectable Circle Gateway option exposed as GatewayWalletBatched.

payTo

Base USDC

GatewayWalletBatched

validated

OpenAPI Contract Inspect the public REST routes, 402 responses, and x-payment metadata. https://api.aitrailblazer.net/openapi.json No-Payment Probe Use an x402-capable discovery client to inspect pricing and payment requirements before paying or attaching a grant token. GET https://api.aitrailblazer.net/v1/readiness Circle Seller Reference Circle Gateway nanopayments seller flow for x402-compatible APIs that accept gasless USDC payments. developers.circle.com/gateway/nanopayments/quickstarts/seller.md Executable Circle-aware Buyer Installable Node.js example with dry-run selection, Gateway-domain signing, explicit payment, and sanitized receipt reconciliation. examples/circle-aware-buyer

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, amount, and payment-path metadata before retry. Standard Base x402 is first for compatibility; Circle Gateway appears second as GatewayWalletBatched for explicit Circle-aware selection.

Circle wallet prerequisiteA Circle-aware signing wallet needs deposited or available Gateway balance. Base ERC-20 USDC alone may return insufficient_balance; that closed failure is not a charge.

Paid retryReturns structured JSON or Markdown evidence after compatible payment proof, with billing metadata that supports per-call reconciliation.

No API keysPublic clients discover and pay through x402 or use signed wallet grant sessions. Delta Signal API keys are first-party operations credentials, not customer integration requirements.

Evidence boundaryOutputs include source dates, caveats, quality flags, and non-advice boundaries. Delta Signal is not a broker, trading bot, wallet, settlement service, or investment adviser.

Review targetValidate ATLAS-7 x402 issuer intelligence first: Readiness, Morning Brief, Company Report, Pressure Board, Alpha Sweep, Quick Ticker Check, Synthetic Basket pressure, and issuer drilldowns.

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 / Circle Settlement

When free or grant-covered calls are unavailable, the route returns a 402 challenge with payment metadata. Standard Base x402 remains first for compatibility; Circle Gateway is an explicit additive path for clients that support GatewayWalletBatched and have available Gateway balance.

402 challenge

Base USDC

verify + settle

receipt

Glama Connector Ownership verified, healthy, Streamable HTTP Connector for the hosted Azure MCP server. glama.ai/mcp/connectors/net.aitrailblazer.api/delta-signal-atlas-7 Remote MCP Endpoint Connect MCP-compatible agents directly to the hosted Delta Signal ATLAS-7 tool surface. https://api.aitrailblazer.net/mcp Open API Spec Inspect the REST, MCP JSON-RPC, composite-tool, daily-monitoring, and audit-status discovery metadata used by validators. https://api.aitrailblazer.net/openapi.json Arazzo Workflow Spec Use scenario pipelines for public MCP x402 handshake, market scans, issuer diligence, daily evidence, and MCP composites. ./arazzo/deltasignal-arazzo.yaml Natural Briefs Quickstart Route examples, response schema, renderer modes, validation model, caching rules, and SDK snippets. ./quickstart.md Agent Rules LLM-readable guidance for Delta Signal Natural Language Briefs, evidence boundaries, and non-advice policy. ./llms.txt

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

Ask help, discover, then execute

Start with MCP deltasignal_help, then 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: # Ask Delta Signal MCP for help and show example prompts. # # Or: # 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.

Run readiness Run Morning Brief View Open API Changelog Read Quickstart Install MCP connector Open Glama connector

Start with readiness through x402 or a signed wallet grant session. Run one bounded brief. Trust the evidence metadata before the narrative.

Delta SignalATLAS-7