Track an account

Add an X account (typically an investor) to your tracked set so its new follows feed every signal endpoint (/follows/new, /follows/enriched, /convergence, /trending, /feed, /discover). Costs 4 credits when the account is new to the platform (a follow baseline is fetched); accounts already in the shared coverage pool are added free. Returns 201 with ready indicating whether a follow baseline already exists; while ready=false the account produces no signal until its first snapshot completes. Handles that fail to resolve on X return 404 and are never billed. New-account introductions are capped per key per day by tier (free 20, starter 100, pro 250, enterprise 2000); adding accounts already in the coverage pool does not count against the cap. Batch: send usernames (alias handles) as an array of up to 50 handles instead of a single username to track them in one call. The single-username shape is unchanged. The batch path always answers 200 with a per-item result because partial success is normal; read each item's status rather than the HTTP code. You are charged per account actually NEW to the platform, not per item submitted. At most 10 new-account introductions are attempted per request (handles beyond that return status "deferred" - resubmit them), and the per-tier daily introduction cap is shared across the whole batch. Account keys are held to the same tracking limit as the web app: Starter 100, Pro 250, custom plan caps apply, Enterprise its own cap; admin keys are exempt. Accounts already over their limit are never trimmed, they just cannot add more. Pro users who turned on automatic expansion (Settings > Billing) go past 250 at $0.25 per account per month, billed like the web app; a batch raises the cap once for the whole batch (one charge). You get 25 free swaps per rolling 7 days (untrack one account, track another, the slot frees immediately). Past that, an account you stop tracking keeps its slot for 7 days before it frees up; re-tracking that same account is always free. Over the limit, a single handle returns 403 with error_code "tracking_cap" (account_limit, tracking, swaps_this_week, free_swaps_per_week, held_slots, overage_hint, and when slots are held hold_note and next_slot_free_at); in a batch that handle's status is "tracking_cap" and the response carries tracking_cap_note.