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.
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.
From filings to usable issuer intelligence
Start with bounded workflows that return structured evidence or readable Markdown, not generic market chatter.
Start here: readiness -> Morning Brief -> metadata
New users should get one successful evidence response before choosing REST, MCP, Arazzo, Glama, or x402 details.
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.
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.
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.
Inspect evidence metadata
Check source dates, caveats, quality flags, evidence hashes, renderer status, and non-advice disclaimers before using the result.
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.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./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.issuer_evidence_envelope, evidence_sections, spectra_metadata, and publication_audit_block./UNIVERSE with structured invalid_path_scope, billing_behavior=not_charged, and cost_usd=0.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.
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.
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.cost_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./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./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.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.These improvements are public integration guidance. Private design-partner names, mailboxes, wallet addresses, grant balances, and support artifacts are intentionally excluded from this page.
Ask for the workflow you want
Composite presets bundle the right evidence routes behind one request, so users do not have to guess endpoint order.
"Give me a Delta Signal morning brief."
Includes readiness, daily changes, risk distribution, top stressed issuers, and alpha opportunities.
"Run a Delta Signal company report for RIOT."
Includes fundamentals, covenant stress, peer ranking, alpha signals, and source metadata.
"Show me the current pressure board."
Includes top stressed issuers, stress tiers, and risk distribution.
"Run an alpha sweep for the current universe."
Includes alpha opportunities, issuer candidates, caveats, and quality flags.
"Quick check MARA before I drill into it."
Includes compact issuer snapshot, stress signal, peer context, and next drilldown options.
"Show peer ranking for BTC-related public companies."
Use after the composite scan identifies which issuer set matters.
Use Delta Signal your way
Start with a bounded workflow, then choose the access path that fits your stack: agent clients, REST APIs, workflow-aware agents, or public x402 routes.
Install MCP connector
REST API
Call Delta Signal directly from your application. Best for backend integrations, dashboards, internal research tools, custom data pipelines, and route-level control.
Open API reference
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 when free calls are exhausted. Compatible clients discover the service, receive an x402 challenge, settle through Base USDC, and retry with proof.
Validate x402 flow
Not sure where to start? Use the composite Morning Brief first through x402/free-tier grant or paid access. Run Morning Brief.
Evidence-preserving outputs
Evidence first. Briefs second. No unsupported invention.
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.
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.
/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.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.
1. Discover
The agent sees the service contract through public metadata and tool discovery.
2. Plan
Arazzo maps user intent to the right scenario pipeline and required inputs.
3. Execute
The client calls one MCP composite or follows the REST sequence step by step.
4. Resolve
Public clients pay when challenged, retry, then receive structured evidence or a compiled brief.
Seven Arazzo-defined agent workflows
These are the machine-readable scenarios agents can inspect before choosing a tool or route sequence.
Canonical agent traces
Concrete examples for how an agent moves from intent to bounded workflow, execution, returned evidence, and renderer rules.
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.
/v1/pricing, OpenAPI metadata, or the x402 challenge before execution.strategix_delta_brief_pdf_full. Produces one polished, branded, auditable PDF per market day from DeltaSignal evidence./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.
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./v1/pricing before execution; for example, live Company Report pricing is currently 0.6 cost_usd.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.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.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.
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.
Granular tools for exact control
Use these after you know which workflow, issuer, or evidence layer you want to inspect.
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.
Build a GET route
Natural Language GET routes use query parameters, not JSON request bodies.
Install in your agent client
Install details come after the first-test and pricing model so you know which path you are enabling.
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.
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
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.
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.
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
Coinbase x402 Docs
Buyer, seller, facilitator, and Bazaar discovery reference for compatible clients.
docs.cdp.coinbase.com/x402
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.
x402 / Bazaar Settlement
When free calls are exhausted, the route returns a 402 challenge with Bazaar metadata and settles paid calls with Base USDC.
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.
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.
Open CLAUDE.md
The Claude Code guide explains MCP install commands, readiness checks, composite-first tool use, x402 boundaries, TripCode caveats, and refusal rules.
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.
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.
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.
Operator and audit workflows
Operational visibility helps confirm whether the ATLAS-7 pipeline is healthy before users depend on live evidence outputs.
Developer copy block: first call
Copy, run, inspect. Start with readiness, then run a bounded workflow through your selected access path.
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.
/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.Start with readiness through the correct x402/free-tier path. Run one bounded brief. Trust the evidence metadata before the narrative.