Skip to main content

For agents (signup + MCP)

/developers redirects here. This is the zero-touch onboarding path.

Bases​

SurfaceURL
Webhttps://new-signal-web.vercel.app
REST APIhttps://new-signal-api.vercel.app
OpenAPIhttps://new-signal-api.vercel.app/openapi.json
Agent indexhttps://new-signal-web.vercel.app/llms.txt
MCP installhttps://new-signal-web.vercel.app/mcp-install.json

1. Request access​

https://new-signal-web.vercel.app/signup?utm_source=agent&utm_medium=docs&utm_campaign=for-agents

Choose the developer role for API or MCP access. Choose data producer to submit the additional feed details required for publishing review. Public catalog and track-record requests do not require a key.

Role guide: trader or agent user reads the public product, developer requests API or MCP access, and data producer applies to publish.

2. Discover the contract​

export WEB="${NEWSIGNAL_WEB_URL:-https://new-signal-web.vercel.app}"
export API="${NEWSIGNAL_API_URL:-https://new-signal-api.vercel.app}"
curl -sS "$WEB/llms.txt" | head
curl -sS "$API/openapi.json" | head -c 400
curl -sS "$API/v1/feeds" | head -c 400

OpenAPI servers[0] is the production API base. Preview deploys may override via PUBLIC_API_URL on the API service.

3. Register MCP (or use REST)​

Use the machine-readable install descriptor:

https://new-signal-web.vercel.app/mcp-install.json

Read mcp.url (and cursorMcpSnippet) for the hosted MCP endpoint. When mcp.url is null, the hosted endpoint is not published yet — use REST from OpenAPI (identical shapes). When set, add it to your MCP host:

{
  "mcpServers": {
    "newsignal": {
      "url": "<value of mcp.url from mcp-install.json>",
      "headers": {
        "Authorization": "Bearer ${NEWSIGNAL_API_KEY}"
      }
    }
  }
}

Call list_feeds, then quote_feed and get_track_record. See MCP for the tool catalog or Agent quickstart for REST examples.

CI / agent smoke: bash scripts/agent-onboarding-smoke.sh (set NEWSIGNAL_WEB_URL / NEWSIGNAL_API_URL for preview).

Next​