EXPLORE ANALYZE API
One toolkit.
Eight fresh perspectives.
Find the right workflow for your question. Explore the inputs, inspect a sample report, and turn evidence into a clear next step.
AI Analysis
Turn unstructured text into useful labels, summaries, and extracted fields.
Explore workflowLLM Analysis
Evaluate answers, compare prompts, and find the regressions that matter.
Explore workflowSEO Analysis
Inspect metadata, links, and page structure. Turn findings into next steps.
Explore workflowWebsite GEO
Understand mentions, citations, and how AI answers represent your content.
Explore workflowSERP Analysis
Explore search results with the query, location, and collection context intact.
Explore workflowKeyword Analysis
Find intent, connect related topics, and build a more useful content map.
Explore workflowGit Repository
Map code, documentation, and tests. Get your bearings in a new repository.
Explore workflowWebsite Analysis
Connect content, navigation, and usability in a clearer website review.
Explore workflowStart with what you need to decide.
A workflow is most useful when the evidence matches the task. Choose SEO for a supplied website audit, keyword analysis for a phrase collection, or LLM analysis for a response evaluated against a rubric. Keep these questions separate even when they share a source.
| Workflow | Typical input | Example output |
|---|---|---|
| AI Analysis | Supplied text, documents, and a task-specific rubric. | Extracted fields with source evidence |
| LLM Analysis | Prompts, generated responses, reference context, and an evaluation rubric. | Criterion-level evaluation findings |
| SEO Analysis | An authorized crawl, supplied HTML, URL inventory, and optional owner-provided search data. | Page-level metadata observations |
| Website GEO | Supplied answer observations, prompt sets, source links, and relevant website content. | Mention and citation observations |
| SERP Analysis | Permitted search-result datasets with query, locale, device, and collection context. | Result-type and destination breakdowns |
| Keyword Analysis | Keyword lists with language, source, and optional documented historical metrics. | Intent labels and ambiguous cases |
| Git Repository | An authorized repository snapshot or file manifest pinned to a known revision. | File-role and component inventories |
| Website Analysis | Supplied page content, authorized browser observations, and a defined review scope. | Navigation and content structure findings |
A shared structure. Different evidence.
The sample reports share a small envelope: the analysis type, a target, an explicit sample marker, findings, and a list of things not measured. Each finding separates observed evidence from a proposed action. That keeps a keyword grouping distinct from a website measurement while making both straightforward to read in code.
The interactive examples are bundled illustrations, not live scans. Their job is to make the workflow tangible before you build a connection to an authorized data source.
Understand the response formatMake your next move
a clearer one.
Explore the workflows. Inspect the evidence. Build something useful.