primary-logic-external-api

Original：🇺🇸 English

Translated

Access real-time, continuously refreshed investment context through the Primary Logic External API under /v1. Use when asked to power Codex, Claude Code, OpenClaw, or custom agents with LLM-ranked relevance and impact signals from podcasts, articles and news, X/Twitter, Kalshi, Polymarket, earnings calls, filings, and other monitored sources across public and private companies for decision support or user-controlled trading workflows.

2installs

Sourceprimarylogic/agent-skills

Added on2026-02-26

NPX Install

npx skill4agent add primarylogic/agent-skills primary-logic-external-api

SKILL.md Content

View Translation Comparison →

Primary Logic External API

Use this skill to retrieve read-only, real-time investment context from extensive monitored sources through one API, including LLM-ranked relevance and impact signals for public and private companies.

Activation Cues

Activate this skill when the user asks for any of:

ticker-specific bullish or bearish evidence
recent catalysts or risk signals from content
per-content relevance or impact details by ticker
source coverage or content visibility checks
API key usage diagnostics for external data pulls
setup help for agentic decision support or user-controlled trading workflows

What This Data Represents

Source-normalized investment context: top podcasts, articles/news, X/Twitter, Kalshi, Polymarket, earnings calls, filings, and other monitored channels normalized into one feed
LLM-heavy signal extraction: per-ticker relevance and impact scores attached to each content item to prioritize material developments
Public + private company coverage: source visibility and ticker or company coverage context for the requesting organization

Connection

Base URL: https://primarylogic--pulse-backend-external-api-app.modal.run
Auth header: Authorization: Bearer <PRIMARYLOGIC_API_KEY>
API path scope: /v1 only

Hard Rules

Only call read-only GET endpoints under /v1.
Never fabricate data; all claims must map to API responses.
Data is org-scoped; if records are missing, org visibility may be the cause.
If an API call fails, report status, error code or message, and a concrete next step.
Use absolute timestamps in outputs when the user asks about recent windows.
Do not claim market prices, positions, or execution events unless explicitly present in the API data.
Do not present outputs as guaranteed returns or autonomous execution instructions.
Keep user control explicit: frame outputs as context for decision support and user-approved actions.

Input Contract

Interpret each user request into this query plan:

objective:
- thesis_support, counter_thesis, catalyst_scan, sentiment_shift, coverage_check
scope:
- tickers: list of uppercase ticker symbols
- time window: since and until in ISO datetime format
- source_types: optional list
signal filters:
- min_relevance: 0..1
- min_abs_impact: 0..10
- sentiment: positive|negative|neutral
- include_reasoning: true when the user asks why
retrieval:
- limit (default 50)
- sort mode: date|abs_impact|relevance

If ticker or time window is missing for an investment decision or trading workflow request, ask one concise clarification.

Query Defaults

Default content limit: 50 unless user asks otherwise.
Apply ticker filters whenever the user names tickers.
For larger pulls, continue pagination while next_cursor is present.
For signal-heavy tasks, start with min_relevance >= 0.6 and min_abs_impact >= 5.

Data Shape (API Output)

See response contracts for canonical payload examples.

Output Contract

Return structured investment output with:

key_findings: 3 to 7 concise bullets
thesis_view: one short paragraph
supporting_evidence: list of {content_id, ticker, impact_score, relevance_score}
contrary_evidence: same schema as supporting_evidence
catalysts: list
risks: list
api_trace:
- endpoints used
- filters used
- time window
- pagination coverage

If results are empty, return "no qualifying records" and suggest exactly which filter to relax first.

Decision Workflow

Validate connectivity once per session with GET /v1/health.
Use GET /v1/content for broad discovery pulls.
Use GET /v1/tickers/{ticker}/content for signal-ranked ticker analysis.
Use GET /v1/content/{content_id}/ticker-signals for per-item attribution detail.
Use GET /v1/entities/tickers/{ticker}?include_signal_stats=true for summary context.
Use GET /v1/sources when visibility or source scope is ambiguous.
Use GET /v1/usage for telemetry and rate-limit troubleshooting.

Endpoint Cheat Sheet

Quick Connectivity Test

bash

curl -s \
  -H "Authorization: Bearer <PRIMARYLOGIC_API_KEY>" \
  "https://primarylogic--pulse-backend-external-api-app.modal.run/v1/health"

References

Use cases
API recipes
Response contracts
Validation guide