FAQ

What is Ticker.id?

Ticker.id monitors U.S. public-company mentions across podcasts and delivers them timely, structured, and verifiable. We find where a company is named in spoken commentary, confirm it's really that company, tie it to the person who said it, and hand you a clean row with a timestamp and a link to the source audio. Ticker.id is API first, and we provide a front-end UI for users to explore much of the data available.

Who is it for?

Anyone who needs to know what was said about a public company, on the record, fast: investors and analysts tracking narrative, funds monitoring their names, developers wiring mention data into their own tools, and researchers studying how stories move. If you follow specific tickers or specific shows, Ticker.id turns hours of audio into spoken-word intelligence you can act on.

Is any of this investment advice?

No. Ticker.id is a monitoring and data tool. We construe and report what was said on public podcasts, with sources you can verify. We do not recommend trades, endorse any host's or guest's views, or guarantee that the underlying commentary is correct. Mentions, sentiment labels, and related outputs may be inaccurate, incomplete, or outdated. We are not a broker-dealer or an investment advisor, and nothing on the Service is financial, legal, tax, or investment advice. Consult a licensed professional before making any financial decision, and treat your use of the Service as your own responsibility. Full language lives in our Terms & Conditions.

Where does the data come from?

Public podcast Really Simple Syndication (RSS) feeds. This is spoken commentary on the record: hosts, guests, and analysts talking. Every source is credited and the original audio is linked so you can listen for yourself. New episodes are polled continuously, so you can use Ticker.id as your podcast player if you like.

Which companies and tickers do you cover?

Publicly traded U.S. companies. The tickers a U.S.-market shareholders would care about.

Which podcasts do you cover, and can I add one?

The podcast universe is enormous, and most of it has nothing to do with markets. So we curate. The catalog is a deliberately chosen set of shows that matter to investors: business, technology, and industry commentary at the core, rounded out with select cross-cultural and news programs that move public companies. It's the same philosophy as the rest of Ticker.id: depth over breadth. We'd rather cover the shows that carry signal than mirror every feed that exists, and we add new ones every week.

Every plan sees the same curated catalog; what scales is how far back you can look. Testing shows a recent window — the greater of the last 15 days or the 15 most recent mentions per ticker — while Terminal, Desk, and Institutional unlock full history.

Want a show we don't carry yet? Registered users add one with the Add show button on the catalog page. Tracking a non-catalog show uses 100 credits per month (about $1.00) at any cadence, and the credits stop the moment enough users track it and it graduates into the main catalog.

What is “depth-now” focus?

The podcast universe is intrinsically broad: millions of hours, overlapping guests, homonyms, off-topic asides, and raw ticker symbols that were never about a stock. Ticker.id aims to deliver signal by aiming resources at delivering depth, in the moment, distilling messy spoken-word content one layer at a time, at scale:

1. Detection — Find candidate mentions.
2. Linking — Decide whether the mention is an investment referent, not a person, place, or homonym.
3. Attribution — Associate the mention to the speaker who said it.
4. Delivery gate — Surface only fully vetted mentions in our search, sheets, and webhooks.

Noise is breadth: raw hits, homonyms, sponsor reads, chatter. Signal is depth-now: verified mentions, timestamp, speaker, and context you can act on.

What counts as a “verified” mention?

A mention is verified once it clears our requirements: detection, disambiguation, attribution to the speaker who said it. An ad read, a false-positive, a low-confidence raw hit are examples of candidate mentions that are treated as noise and filtered by default.

Why did a company get mentioned but not show up as a ticker?

Every mention starts as a candidate and passes through qualifying gates before it becomes a visible row, an alert, or a webhook. Cleaning candidates through our opinionated evaluation loop, the final gate asks one question: is what's being said of interest to a shareholder of this company? If that gate comes back ambiguous, we hold the mention back on purpose rather than guess.

How do you know who said it?

Every episode is diarized, and speakers are identified by role (host or guest) and, where we can, by name. It's an opinionated process we fine-tune constantly. The speaker shows as “Speaker A” rather than a wrong name if our confidence in the attribution is low. The source of truth is always the original audio, linked on every mention, so you can check our work.

What's the difference between the Firehose and a verified mention?

A verified mention has cleared all of our gates. The Firehose is the layer beneath with more raw candidates and low-confidence hits. Verified mentions are delivered with confidence; the Firehose is for users who want to run their own disambiguation and accept the noise that comes with it. The Firehose webhook is available on Desk and Institutional tiers.

Do you label sentiment?

Yes; however, we encourage you to use our data to construct your own sentiment indicators. Ticker.id mentions can carry sentiment labels alongside the speaker, timestamp, and context. Sentiment is in beta on Desk tier and generally available on Institutional; it isn't included on Testing or Terminal tiers. When provided, sentiment is our interpretation as a starting read, not a verdict: it may be inaccurate, incomplete, or outdated. The linked audio is always your source of truth.

What's a ticker sheet?

A ticker sheet is the spreadsheet view for a single symbol: a timeseries of every verified mention of that company, with speaker, show, timestamp, context, and a link to the audio. It's the main surface for reading a company's podcast narrative, and it's where the advertisement filter and other controls live.

What are advertisement filters?

Podcasts blend editorial commentary with sponsor reads, affiliate spots, and paid integrations. We detect those segments by time range, speaker role, and ad-only diarization labels, then separate them from real commentary.

Advertisement filters are the controls that keep sponsor copy out of your view. On any ticker sheet, open Filters in the toolbar and toggle Exclude advertisements. With it on, sponsor reads drop from mention rows, the Firehose, keyword alerts, and any API call that honors exclude_ads.

Filtered by default. New sessions default to ad exclusion because we'd prefer that a stranger landing on a ticker sheet should see investment commentary first, not a mattress ad for some other company. Turn it off anytime to audit sponsor reads or study ad density across shows. See the API docs for the exclude_ads parameter.

How fast does a mention reach me?

Our target is a median of 15 minutes or less from the moment a mention is spoken to the outbound alert. Latency and accuracy pull against each other — the fastest possible alert is rarely the most certain one, and full verification takes time. Managing that tension, shipping fast and right, is the daily job. Real-time alerts require Terminal or above; Testing receives a daily digest. The Service is provided on an “as available” basis; we don't guarantee uninterrupted or error-free delivery.

Can I monitor keywords, not just tickers?

Yes. Alongside per-ticker monitors, you can watch for a keyword or phrase and receive keyword.matched events when it's spoken. Keyword alerts honor the same advertisement filter, so sponsor copy stays out unless you turn exclusion off. Note that tracked-ticker monitors are capped at up to 10 on Testing and unlimited on every paid tier.

Can I get this via API?

Yes. Ticker.id is API-first and the site is just one client of it. The same vetted, timestamped mentions you see in a ticker sheet are available by REST API and as ticker.mentioned and keyword.matched webhooks. Both are signed and both honor exclude_ads.

The API is free to try on Testing — one key, a verified email, and a capped rate over a recent-mentions window; Terminal and above lift the limits and unlock full history. Mint keys in user settings; see the API docs for endpoints and auth. Note that what you're licensed to do with the data is set by the Data License, not the pricing tier — see What am I licensed to do with the data I pull from the API?

How do webhooks and keyword alerts work?

Subscribe to ticker.mentioned for a specific symbol or keyword.matched for a phrase you care about. Each event is signed so you can verify it came from us, targets the same median-15-minute delivery, and respects exclude_ads. The Firehose webhook is available on Desk and Institutional tiers.

How do API keys and rate limits work?

API keys are personal credentials. We store only key metadata such as name, prefix, creation time, plus a hashed secret; the full key is shown once at creation and never again, so save it then. Don't share keys, publish them in client-side code, or use them beyond your tier's documented rate limits. Limits by tier: Testing — 20 requests/minute and 250/day (free to try), Terminal — 120 requests/minute, Desk — 300 requests/minute across three seats, Institutional — unlimited burst. We may suspend keys or accounts that abuse the API or degrade service for others. You can revoke a key anytime in Settings.

What am I licensed to do with the data I pull from the API?

Your plan sets how you access the data (API throughput, credits, seats). Your license sets what you may do with it. The datasets (mention records, ticker-level aggregations, derived metrics) are Ticker.id's property, protected by copyright and database rights. Any paid subscription includes the right to use them commercially inside your own business.

• Included with any paid plan (internal business use): view the data, receive alerts and webhooks, pull it through the API into your own internal tools, and store or cache it in your own systems for your own business, within your tier's limits.
• Requires a separate written agreement (licensing@ticker.id): redistributing, reselling, syndicating, or sublicensing the data to third parties; making it available in a product or service you offer to others; aggregating it for resale; and building or training a competing dataset or model on it.

The line is simple: use the service inside your business freely; anything that puts the data in front of a third party needs a license. Some data may also come from third-party providers under their own terms, which take precedence for that data. Full terms are in the Data License.

How do I add and protect my private podcasts?

You can add your own paid, private podcasts and run them through the same pipeline. Private feeds are available on Terminal tier and up; Desk tier adds priority ingest, and Institutional tier supports a full private corpus of internal and closed shows. Private shows are siloed to your account, never shared, and never enter the public catalog.

How do I manage email and SMS alerts?

Alerts are opt-in, and routing depends on your plan: Testing gets a daily digest, Terminal gets in-app and email, Desk adds Slack and Microsoft Teams, and Institutional supports custom routing. Provide an email or mobile number and choose the monitors you want, and we'll process only the contact details needed to deliver those messages. For Short Message Service (SMS): message frequency varies, message and data rates may apply, reply STOP to opt out or HELP for assistance, and consenting to texts is never a condition of purchase. You can turn off any notification feature at any time from the Tracking or Settings pages.

How do I revoke keys or delete my data?

Revoke API keys anytime in Settings. To request access to, or deletion of, personal information we hold, email service@ticker.id; we'll respond within a reasonable time and as applicable law requires. Some data may be retained where we're required to keep it.

What does Ticker.id cost?

Plans differ by alert volume, API limits, webhook access, history depth, private-podcast support, and data-license scope. Four plans, from free to enterprise:

Desk adds the Firehose webhook and ticker sentiment (beta); Institutional adds Single Sign-On (SSO via SAML/OIDC) with SCIM provisioning, a private corpus, a dedicated pipeline with a named Service-Level Agreement (SLA), a named support engineer, and quarterly reviews. See the Pricing page for the current details.

What are credits, and how do they work?

Credits are a metering currency priced at roughly $0.01 each (100 credits ≈ $1.00). Your plan includes a monthly allotment of 1,500 on Terminal, and 7,500 pooled on Desk. Testing tier grants a one-time 120 at signup; on team plans the pool is shared across seats. Credits pay to track shows that aren't in the catalog yet: a flat 100 credits per month per show, at any publish cadence, until enough users track it and it graduates into the main catalog, at which point the charge stops. In other words, credits let you fund coverage of a show. Terminal's 1,500 credits cover about 15 non-catalog shows a month; Desk's 7,500 pooled credits cover about 75.

What can I do with the data — and what needs a commercial license?

Free viewing gives you a personal, non-commercial look at the data through Ticker.id. Any paid plan adds the right to use the data commercially inside your own business for viewing, alerts, API access, and caching in your own systems, within your tier's limits. What still needs a separate written agreement (licensing@ticker.id) is anything that puts the data in front of third parties: redistributing, reselling, syndicating, or sublicensing it, offering it inside a product or service to others, aggregating it for resale, or using it to build or train a competing dataset or model. You may not remove attribution, and you may not scrape or extract the data by any means other than the API on your plan. We monitor for unauthorized scraping and redistribution, and unauthorized use can end in terminated access and legal action. Some data may come from third-party providers under their own terms, which take precedence for that data. Full terms are in the Data License.

How do you handle my personal data?

We collect what's needed to run the Service: account credentials (email, password, optional display name), API-key metadata plus a hashed secret, usage data, subscription status and tier from our payment provider (never full card numbers), standard technical and log data, and any notification contact details you opt in with. We use it to operate and improve the Service, authenticate you, deliver data and alerts, enforce tiers and billing, and keep the Service secure. Analytics run on Plausible — cookieless and privacy-friendly, with no personal advertising profiles; the only cookies we set keep you signed in. Third-party providers (transcription, LLM, payment, email, SMS, hosting) may process data on our behalf under their own policies. Full detail is in the Privacy Policy; the Service isn't directed to children under 13.

I'm a host or guest named in a mention. What are my rights?

Speakers identified in mention data aren't “users.” What we publish is limited to attributing a public mention to its source: speaker name, podcast title, and timestamp, as it already exists in the public broadcast. We rely on a legitimate-interest basis to report public commentary about public securities, balanced against your rights where the law requires. You can email service@ticker.id to ask what we've published referencing you, request a correction to inaccurate attribution, or request that a particular reference be removed or anonymized. Requests will be weighed against our interest in accurate public reporting.

What are the key terms, warranties, and limits of liability?

Using the Service means agreeing to the Terms & Conditions; you must be at least 13. The Service and all data are provided “AS IS” and “with all faults,” without warranties of any kind. Our total liability is capped at what you paid in the twelve months before a claim, and we're not liable for indirect or consequential damages, with the usual carve-outs (for example, fraud or personal injury) that can't lawfully be excluded. The Terms, Privacy Policy, and Data License are governed by the laws of Texas, U.S. Where the Data License is more specific about dataset use, it controls over the general Terms.

How do I contact you, or report a copyright issue?

General and privacy questions: service@ticker.id. Commercial data licensing: licensing@ticker.id. Copyright complaints, including unauthorized redistribution of data, go to legal@ticker.id under the Digital Millennium Copyright Act (DMCA). Include the work claimed to be infringed, the infringing material and where it is, your contact information, a good-faith statement that the use is unauthorized, and a statement of accuracy under penalty of perjury, signed physically or electronically.