Competitor intelligence, built for agents.
Cyte is competitor intelligence for online presence. Every step of the loop — track, compare, detect, act — is exposed to agents through a REST API (read + write), a published OpenAPI spec, JSON-LD on every page, and llms-full.txt at the root. No browser in the loop.
Behind it, Cyte runs thousands of its own AI agents for every customer, around the clock, on competitor analysis. If your agent needs that signal — or needs to know what to change — this page is the contract.
What an agent can do with Cyte.
Read where a brand stands against each competitor, open the comparison, pick up what competitors changed, and fetch the day's ideas — all without a browser in the loop.
REST API (read + write)
Pull projects, prompts, runs, competitors, topics, changes, and ideas — and POST to create projects. JSON over HTTPS, versioned endpoints, predictable pagination. Base URL: app.cyte.si/api/v1.
Structured LLM-readable content
Every page emits JSON-LD schema. /llms.txt summarizes the site. /llms-full.txt ships the full factual base in one request. No scraping required.
Bearer-token auth
Per-workspace API keys, issued from Settings > API Keys in the app. Encrypted with AES-256-GCM. Rotate any time. Send as Authorization: Bearer <api_key>.
Deterministic CSV export
Stable column schemas for prompts, runs, citations. Diffable across runs. Safe to treat as a tabular source in retrieval pipelines.
Competitor intelligence reads
Competitor teardowns, the topic coverage map, the ranked change feed, and the day's ideas with their action briefs — each with its evidence and a confidence level. Available on Plus and above.
Citation source reads
For every answer, Cyte records which pages are cited. An agent can read which pages feed AI answers in a category — for the brand and for each competitor — and see where the brand is missing. Social media tracking is planned, not built.
Which surface, which plan.
Everything public stays public. Everything scoped to a workspace requires a token. Everything that changes state requires write access.
Rate limits are per-token. Exact numbers published in the API reference at docs.cyte.si (alongside GA).
One request. Full factual base.
An agent that needs to answer “what is Cyte, what does it track, and how does it score visibility” can fetch /llms-full.txt once. No JavaScript execution. No DOM traversal.
The read surface, enumerated.
Base URL: https://app.cyte.si/api/v1. Every endpoint returns JSON and accepts Authorization: Bearer <api_key>. Full OpenAPI spec: app.cyte.si/openapi.json.
Core concepts: a prompt is a search query users ask LLMs. A run queries all active LLMs with all tracked prompts and scores the results. Scores (0–100) combine mention, position, frequency, and sentiment. A topic is a subject covered on the brand's site or a competitor's. A change is a detected edit to a competitor's site. An idea is a specific thing to change on the brand's own site, with its evidence and an action brief.
Reads for topics, changes, and ideas are available on Plus and above. The table above lists the endpoints documented publicly today.
Why agents get reliable data out of Cyte.
Agent-accessibility isn't an export feature. It's a writing discipline applied to every page.
Every page leads with a declarative fact. Pricing, formulas, limits, and methodology are stated in plain numbers, not marketing language. Agents extract the same answer humans do.
Cyte Score math lives on /methodology. Glossary lives on /glossary. Comparisons live on /compare. When an agent retrieves, it lands on a canonical page — no content duplication across routes.
Blog posts, changelog entries, and legal pages all carry visible datePublished and dateModified. Agents can resolve freshness without guessing.
Comparison tables on /compare render as semantic <table>, not CSS grids of <div>. Downstream extraction preserves rows and columns.
Third-party stats cite their source (publication and date). Agents can propagate provenance without losing it.
Every page owns its canonical URL. No trailing-slash drift, no campaign parameters in sitemaps, no redirect chains. Bookmark-safe for agent memory.