This is an inventory of our records, not an assessment of ACIW. It says nothing about how ACIW appears inside ChatGPT, Claude or any other AI product — nothing outside those systems can measure that, and we will not pretend otherwise.
Services we offer, not things ACIW has failed to do.
Live means a person's assistant fetched this record on their behalf. Crawlers are indexing bots. The rest is browser and API traffic. These count requests to Origin — they are not a measure of how often anyone asks an AI about ACIW, and we have no way to measure that.
A machine cannot check a PDF against anything. Turning ACI WORLDWIDE, INC.'s filings into a signed, structured record that anyone can verify took the work below — and this is what a reader gets in return.
| SEC EDGAR extraction | 242 filings indexed |
| AI profile generation | ~$0.10 (Claude Sonnet) |
| IR site scraping | Custom navigation scripts |
| Multi-attempt extraction | 2 calls over multiple sessions |
| Stock quote pipeline | Daily EOD automated |
| Origin chain signing | Every response anchored |
| Fact extraction | 25 facts, 23 topic categories |
Your IR site required custom scripts and multiple scrape sessions to extract data.
| Company identity | ~200 tokens |
| Full profile (people, products) | ~800 tokens |
| Filing index (242 filings) | ~500 tokens |
| Stock quote with provenance | ~150 tokens |
| Latest quarter facts | ~500 tokens |
| Topic search (cross-company) | ~300 tokens |
| Total per review | ~2,450 tokens |
| Time to answer | 2–4 seconds |
| Cost per query | < $0.01 |
| Provenance | Full chain to SEC.gov |
4-5 API calls. Structured JSON. Every response signed. Agent gets exactly what it needs — not a 200-page PDF. Full dataset available: 25 facts from 2 earnings calls, all pre-extracted and ready.
A standard quarterly review costs ~136K tokens without Origin (finding the IR site, parsing PDFs, extracting data). With Origin: ~2,450 tokens for the same information — structured, signed, verified. Plus access to 25 pre-extracted facts from 2 earnings calls whenever the agent needs deeper analysis. Your IR site requires custom work to scrape. We built the pipeline.
An AI agent doesn't fetch everything at once. It asks specific questions. Here's the real per-query cost:
| Question | Via Web Search | Via Origin | Savings |
|---|---|---|---|
| "Who is ACIW?" | 10,000–50,000 tokens | ~200 tokens | 50–250x |
| "Latest stock price?" | 5,000–20,000 tokens | ~150 tokens | 33–133x |
| "Key people and products?" | 15,000–40,000 tokens | ~800 tokens | 19–50x |
| "What did ACIW say about [topic]?" | 30,000–100,000 tokens | ~300 tokens | 100–333x |
| "Show me SEC filings" | 8,000–25,000 tokens | ~500 tokens | 16–50x |
Web search: agent must discover URL, render JavaScript, parse HTML, extract data, hope it's current. Origin: structured JSON, 2-4 seconds, full provenance chain. Full dataset: 25 facts from 2 earnings calls available on demand.
Today, AI agents are the fastest-growing audience for investor data. But most IR sites were built for humans reading in browsers. AI agents need structured, discoverable, verifiable data. Here's your roadmap:
Add a single JSON file at www.aciworldwide.com/.well-known/ai that tells AI where to find your data. Think of it as robots.txt for AI — instead of telling crawlers what NOT to read, it tells AI agents what TO read and where.
Time to implement: 10 minutes. One JSON file, no code changes.
Copy this JSON to www.aciworldwide.com/.well-known/ai
{
"schema_version": "1.0",
"name": "ACI WORLDWIDE, INC. \u2014 Investor Relations",
"verified_by": "origin.rootz.global",
"investor_relations": {
"profile": "https://origin.rootz.global/api/company/ACIW",
"filings": "https://origin.rootz.global/api/company/ACIW/filings",
"quotes": "https://origin.rootz.global/api/company/ACIW/quote",
"transcripts": "https://origin.rootz.global/api/company/ACIW/transcripts",
"signals": "https://origin.rootz.global/api/signals?ticker=ACIW",
"static_page": "https://origin.rootz.global/static/company/ACIW.html"
},
"provenance": "SEC-derived data carries an origin leaf: sha256(content + parent + timestamp), plus the EDGAR accession it came from. The leaf is our hash, not a signature from the SEC — verify by re-fetching the accession from sec.gov.",
"contact": "discover@rootz.global"
}
This is the company stating, on its own domain, where its machine-readable investor data lives and who signed it. Any agent that looks for it finds a signed copy. Whether a given agent looks is that agent's decision, not something this file compels.
AI agents struggle with PDFs, webcasts, and JavaScript-rendered pages. The highest-impact change: publish machine-readable versions of your most-requested content.
| Document | Current Format | AI-Ready Format |
|---|---|---|
| Company overview | HTML (often JS-rendered) | Markdown file or FAQ JSON — AI reads these natively |
| Earnings transcripts | Markdown + JSON with speaker tags and key metrics | |
| Business description | Buried in 10-K PDF | Standalone MD file updated quarterly |
| FAQ | HTML accordion (often invisible to AI) | JSON-LD FAQ schema — search engines already support this |
| Press releases | HTML (varies by platform) | Structured with date, type, headline, summary fields |
Why Markdown? Every major AI model reads Markdown natively. It's the universal language of AI communication. A business-description.md on your IR site is instantly consumable by Claude, GPT, Gemini, Grok — no parsing needed.
AI agents are already citing your company data. The question is whether that data has a verifiable chain back to you. Origin anchoring binds your investor data to your corporate identity — so every fact carries proof of where it came from.
Data with origin is more trustworthy than data without origin. When an AI reads your anchored data, it knows the chain is real — and it carries that chain forward to everyone who reads its output.
Join our IR for AI program — we handle the setup.
Once your data is anchored with origin, you need to see who's reading it. Program members get:
No other service provides AI traffic analytics for investor relations. This data doesn't exist anywhere else.
Program members get guaranteed scanning, capture, and origin anchoring:
| Property | Finding |
|---|---|
| IR Domain | www.aciworldwide.com |
| AI Accessibility | moderate — Some transcripts found |
| Transcripts | ✓ PDFs found |
| Press Releases | ✓ Found (16) |
| IR Platform | Unknown |
| Last Scanned | 2026-04-13 06:50:03 |
Get this record summary for ACIW delivered to your inbox — share it with your IR team.
No signup needed — your data is already partially accessible via the Origin API:
| Data | Status | Link |
|---|---|---|
| Company identity | ✓ SEC-verified | View JSON |
| AI profile | ✓ Extracted | View JSON |
| SEC filings | ✓ 242 indexed | View JSON |
| Stock quote | ✓ Daily EOD | View JSON |
| Transcripts | ✓ 2 calls | View JSON |
| Earnings calendar | Next: 2026-09-19 | View JSON |