deltasignal-atlas-7

name: deltasignal-atlas-7 description: Use DeltaSignal ATLAS-7 for SEC-grounded issuer intelligence on crypto public companies, including composite MCP presets, readiness, covenant stress, top-stressed issuers, peer ranking, alpha signals, fundamentals, compact daily SEC monitoring, paginated evidence drilldowns, and Azure-native audit status over the free starter tier, Tempo MPP, or Base x402.

DeltaSignal ATLAS-7

Use this skill when the user asks for DeltaSignal, ATLAS-7, crypto public issuer stress, SEC-grounded crypto equity intelligence, covenant stress, top-stressed issuers, issuer fundamentals, or DeltaSignal paid API access.

Access Model

DeltaSignal is a usage-based intelligence API with a free starter tier. Do not imply there is a subscription requirement.

Free tier:

• The Base x402 /v1/* routes allow 5 free calls per user before payment fallback.
• If the free tier is exhausted, the same route returns x402 payment requirements for compatible clients.
• If a caller includes an x402 payment header, treat it as an intentional paid request rather than consuming free quota.

Primary rail:

• Tempo MPP routes under https://api.aitrailblazer.net/mpp/v1/*

Agentic Market compatibility rail:

• Base x402 routes under https://api.aitrailblazer.net/v1/*
• Base network: eip155:8453
• Payment asset: USDC

Bundled MCP server:

• Treat DeltaSignal as an MCP-first plugin. Prefer named MCP tool calls over hand-written HTTP routes whenever the plugin is installed.
• Public MCP initialize and tools/list are free discovery methods. Public MCP tools/call remains protected by x402 payment unless a free-tier grant applies.
• Prefer composite MCP presets for common workflows:
  • deltasignal_morning_brief for daily scans.
  • deltasignal_company_report for full ticker reports.
  • deltasignal_pressure_board for risk monitoring.
  • deltasignal_alpha_sweep for opportunity screening.
  • deltasignal_quick_ticker_check for fast ticker checks.
  • deltasignal_daily_changes for compact Daily Monitoring.
  • deltasignal_daily_change_evidence for explicit issuer proof after a monitoring result.
  • deltasignal_atlas7_audit_status for operator checks that the Azure-native 215-issuer regression audit is healthy and fresh.
• Use granular tools only for custom drilldowns or when a composite preset is unavailable.
• Prefer the deltasignal_* MCP tools when this plugin is installed and the request maps to a supported DeltaSignal route.
• MCP tools are read-only, idempotent, closed-world tools with strict argument validation.
• In live mode, the MCP wrapper calls the deployed Base x402 /v1/* routes and returns free-tier headers or x402 payment requirements in the tool result.
• In internal mode, the MCP wrapper uses a pre-authorized DELTASIGNAL_API_KEY against the deployed API for no-payment smoke testing.
• In local mode, the MCP wrapper calls http://127.0.0.1:8080/v1/* without x402 payment so DeltaSignal can be used during development work.
• If the MCP wrapper returns payment_required, do not claim payment succeeded. Tell the user the free tier is exhausted or unavailable and switch to an x402/MPP-capable payment flow.

Do not translate between route families unless the user explicitly switches payment rails. If the active client is Agentic Market or Coinbase x402, use /v1/*. If the active client is MPPScan, mpp.dev, or asks for Tempo MPP, use /mpp/v1/*.

Composite Presets

Composite presets are discounted server-enforced workflows. Public Builder pricing uses 1 credit = $0.01 of DeltaSignal usage value. Credit packs are not implemented yet.

Daily Monitoring and Evidence are separate products. deltasignal_daily_changes is compact by default and should not be used as a bulk evidence export. Use deltasignal_daily_change_evidence only when the user asks to inspect raw proof for a named issuer or CIK.

TripCode Research Continuity

Use TripCode tools when a user has a DeltaSignal article subtitle with ATLAS-7 TripCode: TF-SUB-... and wants Codex or Claude Code to load the machine-readable research object behind the article.

Important rules:

• First confirm the live MCP tools/list exposes the TripCode tool you intend to call. Local/source proof, planned tools, or stale public MCP output are not enough to claim public production availability.
• TF-SUB resolves DeltaSignal article/research objects stored in Azure Blob.
• TF-XBRL resolves SEC/XBRL evidence nodes and must preserve SEC identifiers.
• TF-DS is reserved for computed DeltaSignal signal nodes.
• TF-RIVER is reserved for issuer thesis River nodes.
• Substack post IDs, URLs, slugs, and publication times are secondary publication metadata. They must not define or change the TF-SUB TripCode.
• If a resolver returns missing evidence, say it is missing. Do not invent article objects, filing evidence, or River state.
• If the public MCP surface does not expose TripCode tools, use the supported ATLAS-7 issuer workflow instead: company report, fundamentals, covenant stress, peer ranking, alpha signals, SPECTRA field map, and daily-change evidence.
• For the HUT proof path, missing trendforge/v1/resolver/objects/TF-RIVER/TF-RIVER-HUT.json or trendforge/v1/resolver/indexes/by_issuer/HUT.json means River continuity is unavailable until those deployed blobs exist.

TripCode tool pricing:

Operator Audit Status

• Use deltasignal_atlas7_audit_status when the user asks whether ATLAS-7 is healthy, current, monitored, Azure-native, or fully regression-tested.
• Treat it as an operational readiness/audit surface, not as issuer intelligence or investment evidence.
• Preserve status, stale, artifact.prefix, finished_at_utc, issuer_count, operation_count, failed_count, historical_failed_count, and composite_failed_count when summarizing.
• A healthy result currently means the latest scheduled Go audit covered the 215-issuer universe, current routes, historical routes, and composite MCP workflows with zero failures inside the freshness window.
• If the route returns unauthorized from the bundled STDIO wrapper, explain that this operator endpoint requires internal/pre-authorized access and tell the user to use the hosted MCP/tooling path that already has the DeltaSignal credential.

Paid Routes

Use readiness before higher-cost calls when freshness matters.

When exact quote, budget-gate, or reconciliation accuracy matters, fetch GET https://api.aitrailblazer.net/v1/pricing first and treat it as the authoritative runtime route catalog. Read routes[].route_uri, routes[].method, routes[].price_usd, ticker/scope metadata, and the declared canonical cost field instead of relying on a hardcoded local table. Cache only by the returned contract/version metadata or refresh per run.

Supported list filters include limit, offset, risk_tier, min_stress, linkbase_only, and debt coverage status filters where exposed by the route.

Future artifact-backed bulk daily evidence exports are not inline chat responses. Proposed prices: small pack $0.15, standard pack $0.30, full daily evidence export $0.75-$1.50.

Operating Rules

• Confirm whether the request should use remaining free calls or a paid rail before initiating payment.
• Confirm the route family and approximate cost before initiating any paid request.
• Never invent a payment result. Report the route, status, payer/payment metadata if available, and the response summary.
• Treat DeltaSignal outputs as issuer intelligence, not investment advice.
• Preserve source dates, row counts, readiness fields, risk tiers, and debt coverage status when summarizing.
• For named issuers, normalize tickers to uppercase before constructing routes.
• For large endpoints such as company-report and daily-changes, do not pipe npx agentcash fetch stdout directly into another process; write the response to a file or use compact/paginated routes to avoid Node/pipe truncation around 64 KB.
• Keep universe routes path-ticker-free. Do not append /UNIVERSE, /{ticker}, or any other path segment to GET /v1/readiness, GET /v1/alpha-opportunities, GET /v1/top-stressed, GET /v1/risk-distribution, or GET /v1/daily-changes/latest; use query parameters such as limit or offset where supported.
• Use GET /v1/pricing as the upstream discovery source for live route prices. Treat hardcoded prices in client code or docs as fallback hints only; budget gates should prefer the live price_usd for the route/method being called.
• Use GET /v1/contract/fields as the upstream discovery source for parser-stable fields. Load-bearing paths include readiness ok, age_minutes, and freshness_window_hours; generic ticker, route_uri, and source_date; company-report summary.current_read, summary.issuer_state, summary.subscriber_takeaway, confidence, data.ticker, data.workflow, data.status, and mcp_summary; daily-changes row-level ticker; and stress compatibility fields stress_50pct / stressed_leverage_50pct.
• For terminal MCP-brokered ATLAS datasets, use GET /v1/contract/fields and its terminal_broker object as the source of truth. Current deltasignal-terminal-broker-v1 covers covenant-stress, alpha-signals, and company-fundamentals; terminal clients should key opaque summaries by endpoint_id and preserve only status, cache_status, quote_status, summary / evidence_summary, estimated_usd / cost_usd, and confirmation_token.
• Treat structured not_found responses as soft misses, not hard failures. If a ticker-scoped route returns status=not_found, preserve reason, coverage_state, retry_after_days, route_uri, ticker/request key, and billing_behavior; do not retry that same endpoint/ticker pair until the retry window expires unless the user explicitly asks.
• Current SPECTRA semantics: IREN is a supported field-map ticker; unsupported field-map tickers return reason=historical_field_map_contract_missing, coverage_state=not_available_for_issuer, retry_after_days=7, billing_behavior=not_charged, and cost_usd=0.
• For billing reconciliation, use numeric cost_usd as the canonical ledger field on successful protected /v1/ JSON object responses. Treat quoted_cost_usd and actual_cost_usd as supplemental diagnostics: settled x402 calls should report the settled price, while API-key, internal, or grant-covered calls may preserve the route quote in quoted_cost_usd and return cost_usd=0 / actual_cost_usd=0.
• If payment tooling is unavailable, give the exact route and expected cost, then explain that payment execution needs an x402 or MPP-capable client.

Common Prompts

• "Give me a DeltaSignal morning brief" -> call deltasignal_morning_brief.
• "Run a company report for RIOT" -> call deltasignal_company_report with ticker=RIOT.
• "Show the pressure board" -> call deltasignal_pressure_board.
• "Find alpha opportunities" -> call deltasignal_alpha_sweep.
• "What changed today?" -> call deltasignal_daily_changes.
• "Show me why ARKB moved" -> call deltasignal_daily_change_evidence with ticker=ARKB and the source date from Daily Monitoring when available.
• "Is the full ATLAS-7 audit healthy?" -> call deltasignal_atlas7_audit_status.
• "Load this article TripCode TF-SUB-..." -> call deltasignal_resolve_article_tripcode.
• "Compare this article TripCode to its filing evidence" -> resolve the TF-SUB object, resolve linked TF-XBRL objects, then call deltasignal_compare_article_to_filing_evidence.
• "Discover prior articles in this issuer River" -> call deltasignal_list_article_tripcodes with current_tripcode, river, or issuer.
• "Resolve this River TripCode" -> call deltasignal_resolve_river_tripcode.
• "What changed across this issuer River?" -> call deltasignal_reverse_search_river.
• "Search this River for a claim" -> call deltasignal_search_by_claim.
• "Compare this claim to evidence" -> call deltasignal_compare_claim_to_evidence.
• "Build the thesis map from this article TripCode" -> call deltasignal_list_article_tripcodes first when prior nodes are not supplied, then call deltasignal_article_thesis_map with the article TripCode and discovered River/evidence continuity.
• "Generate a TripCode for this draft article" -> call deltasignal_generate_article_tripcode with ticker, title, research_slug, research_date, and optional research_version.
• "Quick check MARA" -> call deltasignal_quick_ticker_check with ticker=MARA.
• "Is DeltaSignal current?" -> call readiness.
• "Which issuers are most stressed?" -> call top-stressed.
• "Run covenant stress on MARA" -> call covenant-stress detail for MARA.
• "Show high-risk linkbase-backed issuers" -> call covenant-stress list with risk_tier=HIGH, min_stress, and linkbase_only=true.
• "Compare MARA to peers" -> call peer-ranking for MARA.