Skip to content

Bring your agent

Connect YOUR agent to YOUR brokerage, and point it at our feed. We publish; your agent decides.

impersonalpull-onlycounsel-gated

How it works

Three steps

  1. Open your brokerage's agentic account. On Robinhood this is a one-time desktop step: open the ring-fenced Agentic account, fund it with what you choose, and connect your agent per their onboarding. Your agent can only trade inside that account, and only for you.
  2. Mint your feed key. Sign in with your wallet, then create a digest key in account settings (POST /api/digest/keys). The key is shown once; it authenticates your agent's reads and nothing else — every key receives byte-identical editions.
  3. Give your agent the reading template below and fill in your own rules. The template contains no trading rules from us — it is a feed-reading harness, and your rules stay yours.

The reading template

Copy for your agent

You are my trading research reader. Once per day after 17:35 ET,
fetch https://wager.top/api/digest/latest with header
"Authorization: Bearer <MY_DIGEST_KEY>".

The response is wager.top's impersonal digest — the same bytes every
subscriber receives. It contains no trading instructions. Evaluate it ONLY
against MY OWN rules below, and act ONLY through MY OWN brokerage agentic
account under MY standing instructions.

MY RULES (I wrote these; wager.top did not):
- <your entry rules>
- <your risk limits — max position size, max daily loss>
- <your exit rules>
If the feed is unavailable or empty, do nothing.

What this is — and is not

Plain terms

  • We publish the same editions to every subscriber, on a fixed schedule. Nothing is tailored to you, timed for you, or prioritized for anyone.
  • Your agent and its instructions are yours. We never see, hold, or touch your brokerage account, its credentials, or its tokens.
  • The feed serves only published editions; before the publication gates open (including legal review), agents receive a uniform "digest_unavailable" response.
  • Editions may be empty — an empty edition on schedule is normal and means "no qualifying signals" or "a data right was unavailable," stated as such.

Details

API surface
  • GET /api/digest/latest — the most recent published edition. Bearer key auth. Poll after 17:35 ET; polling more often returns the same bytes (uniform rate limits apply).
  • GET /api/digest/{slot_key} — a specific edition by slot key (digest-YYYY-MM-DD).
  • POST /api/digest/keys · DELETE /api/digest/keys/{prefix} — mint and revoke your keys from your wallet session. Keys are stored hashed; the plaintext is shown exactly once.