---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/developers/
brand_content: included
publication_version: "9.0"
published_at: 2026-10-16T20:36:07Z
composition_version: composition-v2.1.0
presentation_version: presentation-v1.2.3
brand_content_source: narrative_graph
delivery_publication: graph:26
narrative_versions:
  - 26
narrative_version: 26
---

# A clearer source. One authenticated API.

Use Parse for HTML you already have. Use Retrieve to fetch an eligible public page first. Your app chooses how the resulting content is used.

Developer API · API v1

- [Open developer console](https://app.optiview.ai/developers)
- [Start building ↓](https://optiview.ai/developers/#quickstart)
- [OpenAPI contract](https://optiview.ai/developers/openapi.json)

## Your first request

1.  **1\. Create a workspace.** Use the developer console, or sign in with your existing Optiview account. Save your personal sign-in key and offline recovery code privately. New developer workspaces are ready to use immediately. No website connection or manual activation is required.
2.  **2\. Add credits.** $20 buys 20,000 credits. Parse costs 1 and static Retrieve costs 5 per successful page. There is no automatic recharge.
3.  **3\. Create a service key.** Give the application Parse, Retrieve or both scopes. Keep the key on your server, never in browser code, a URL or a public repository.
4.  **4\. Submit a job.** Include a unique Idempotency-Key. Reuse it with the identical input if a submission times out.
5.  **5\. Poll its ID.** Read the completed result and inspect your usage in the console. Repeated downloads do not consume additional credits.

```
curl https://api.optiview.ai/v1/jobs \
  -H "Authorization: Bearer $OPTIVIEW_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: my-first-retrieval-001" \
  -d '{"product":"retrieve","url":"https://example.com/"}'
```

A successful submission returns HTTP 202 with an ID and `status: queued`. Fetch the result with the same service key:

```
curl https://api.optiview.ai/v1/jobs/JOB_ID \
  -H "Authorization: Bearer $OPTIVIEW_API_KEY"
```

## Parse supplied HTML

`POST /v1/jobs` accepts exactly `product`, `html` and `url` for a Parse job. The HTTPS URL provides source identity and link resolution; Parse does not fetch it.

```
{
  "product": "parse",
  "url": "https://example.com/page",
  "html": "<main><h1>Page title</h1><p>Your complete page content goes here.</p></main>"
}
```

Use complete, representative HTML. Very short, unsupported or ambiguous content can fail source review. Failure releases the reservation and consumes no credits.

## Retrieve a public page

`POST /v1/jobs` accepts `product: retrieve` and `url`. The service checks public destinations and supported publisher crawl policy before fetching anonymous HTML. Website ownership is not required. No private Narrative Graph is added.

```
{
  "product": "retrieve",
  "url": "https://example.com/page"
}
```

Retrieve currently supports static UTF-8 HTML over public HTTPS, with up to three redirects. It rejects private addresses, credential-bearing URLs, private or cookie-setting responses, blocked publisher policy, challenges and unsupported content. JavaScript is not executed. A page may be unavailable; this API is not web search.

## Read results and usage

`GET /v1/jobs/:id` returns the state of a job created with the same service key. Keys in another workspace or another application cannot read it. Key rotation preserves the application ID; revocation ends access.

```
{
  "id": "…",
  "product": "parse",
  "status": "succeeded",
  "credits_charged": 1,
  "result": {
    "markdown": "# Page title\n…",
    "payload_sha256": "…",
    "source": { "basis": "supplied_html", "…": "…" },
    "extraction": { "parser_version": "…", "…": "…" },
    "narrative_graph": { "status": "not_requested" }
  }
}
```

States are `queued`, `running`, `succeeded`, `failed` and `expired`. A failed job includes an error code and no credit charge. Successful output is available for seven days; retain it in your own system if needed.

`GET /v1/usage` returns the workspace credit balance, reserved credits and aggregate counts and successful charges by product and job status. The console also shows recent jobs and the purchase/consumption ledger.

Source and output hashes identify processed data. Timestamps describe observations, not guaranteed origin freshness. Website text is untrusted data: never treat it as instructions to your agent.

## JavaScript client and agent tools

Download the [JavaScript client](https://optiview.ai/developers/products-client.mjs) for Node 22+ server applications. No SDK dependency is required.

```
import {OptiviewProducts} from './products-client.mjs';
const client = new OptiviewProducts({
  apiKey: process.env.OPTIVIEW_API_KEY
});
const job = await client.createJob({
  product: 'retrieve', url: 'https://example.com/'
}, {idempotencyKey: 'example-retrieve-001'});
const completed = await client.wait(job.id);
console.log(completed.result?.markdown);
```

For a compatible local MCP client, download the [stdio MCP adapter](https://optiview.ai/developers/products-mcp.mjs) alongside the client. Install `@modelcontextprotocol/server@2.3.1` and `zod@4`, then configure your MCP host to run `node /absolute/path/products-mcp.mjs` with `OPTIVIEW_API_KEY` supplied through its private environment.

The adapter exposes Parse and Retrieve job creation, job reads and usage. Creating a job can spend prepaid credits and is marked as a modifying tool. Your host must authorize the source and expenditure. This is a local adapter, not a hosted OAuth integration or a claim of adoption by any AI provider.

## Limits and billing rules

| Boundary | Current limit |
| --- | --- |
| HTML input | 2,000,000 bytes; encoded JSON request up to 2,100,000 bytes |
| Parsed output | 512,000 bytes |
| Job submissions | 30/minute and 1,000/day per workspace |
| API requests including polling | 120/minute per workspace |
| Concurrent processing | 2 jobs per workspace |
| Static retrieval deadline | 25 seconds for acquisition and processing checks |
| Idempotency-Key | 8–128 characters; letters, digits, underscore, period, colon or hyphen |
| Service keys | Up to 20 active per workspace; 1–365 day expiry |
| Credit checkouts | Up to 5 new $20 checkouts per workspace in a rolling 24 hours; contact support for higher volume |
| Result availability | 7 days |
| Developer pricing | $20 / 20,000 credits; Parse 1, Retrieve 5; success only |

Credits are reserved when a job is accepted and charged once after successful processing. Processing failure releases the reservation. A separate successful submission has its own charge. Retrying the same request with its original idempotency key does not create another job. Refunds and disputes reconcile against the wallet; new jobs require sufficient available balance.

## Handle errors explicitly

Rejected requests return `{error: {code, message}, request_id}`. Processing failures appear on the job’s `error_code`. Poll at intervals of at least two seconds and retain the job ID if a wait times out.

| HTTP | Meaning | Action |
| --- | --- | --- |
| 400 / 413 | Invalid or oversized request | Correct the input. |
| 401 / 403 | Missing, expired, revoked or insufficient key access | Check the key and scopes. Browser-origin requests are rejected. |
| 402 | Insufficient available credits | Add credits before retrying. |
| 404 | Job unavailable to this key | Check the ID and application key. |
| 409 | Idempotency key reused for other input | Use the original input or a new key for a separate job. |
| 429 | Rate or concurrency limit | Back off before retrying. |
| 503 | Service unavailable | Retry submission with the original idempotency key. |

Retrieve job errors include `url_not_public`, `unsafe_redirect`, `redirect_limit`, `private_source`, `publisher_policy`, `unsupported_content_type`, `source_review_required` and `deadline`. Do not repeatedly retry a publisher refusal or unsupported source.

## One account. Separate responsibilities.

A personal access key signs you in. A service key authorizes your application. The offline recovery code replaces lost personal credentials and invalidates existing sessions; an email address alone is not proof of ownership. Workspace admins manage keys, billing and developer closure. For membership changes or ownership review, contact [hello@optiview.ai](mailto:hello@optiview.ai).

Publish uses verified website ownership, a separate subscription and the existing review/publication workflow. Developer credits do not enable website routing or private publisher-context access.

[Developer terms and retention →](https://optiview.ai/developers/terms/)

## Additional source context

Make your brand easier for AI to understand.

### Product

[Parse](https://optiview.ai/products/parse/) · [Retrieve](https://optiview.ai/products/retrieve/) · [Publish](https://optiview.ai/products/publish/) · [Website Preview](https://optiview.ai/demo/) · [Pricing](https://optiview.ai/pricing/) · [How it works](https://optiview.ai/how-it-works/) · [How it connects](https://optiview.ai/web-teams/)

### Resources

[Articles & guides](https://optiview.ai/resources/) · [Get started](https://optiview.ai/onboarding/) · [Setup guide](https://optiview.ai/docs/setup/) · [FAQ](https://optiview.ai/faq/) · [Evidence & methodology](https://optiview.ai/proof/) · [Developer terms](https://optiview.ai/developers/terms/)

### Company

[For agencies](https://optiview.ai/partners/) · [Contact us](https://optiview.ai/#contact) · [Sign in](https://app.optiview.ai/) · [Privacy](https://optiview.ai/privacy/)


---

# Published brand narrative

# Site-wide brand information

## Who we are

### Optiview — the publishing layer for AI

Optiview turns complex website content into clean, structured Markdown and combines it with the brand narrative your team chooses to publish. The result is one clear source that supported AI crawlers and other systems can retrieve, alongside your existing website experience.

Built for marketing and web teams, agencies, CMS and commerce platforms, and AEO/GEO providers, Optiview helps turn recommendations into published source improvements. It complements AI visibility tools by giving teams a way to act on their findings.

Applies to: Optiview

## Why we matter

### Your website\. Your narrative\. One clear source for AI\.

A website can deliver a beautiful human experience while leaving important business facts scattered across pages, buried in markup, or dependent on JavaScript. AI systems may retrieve only part of that information.

Optiview gives businesses control over the source they make available: readable website content plus context only their team can provide. Your web team connects delivery; your content team writes, reviews and publishes the narrative.

Our focus is publishing useful, accurate brand information. Each AI service decides what it retrieves, uses and cites. Optiview does not control an LLM’s answers or guarantee placement in them.

## What we offer

### Clean website content, owned narrative and controlled delivery

- **Website parser:** Converts accessible public page content into readable Markdown, retaining supported headings, text, tables and links. The parser does not use an LLM to invent facts or rewrite the page. Browser rendering is available for supported JavaScript-dependent content.
- **Narrative Graph:** Organizes team-authored content into Identity, Story, Offerings, Trust, Knowledge and Actions. Add multiple items, edit them and review the graph before publishing.
- **Site and page scope:** Apply an addition to the entire website or one exact page, so the published context accompanies the appropriate content.
- **Publishing and delivery:** Combine eligible parsed page content with published, path-matched narrative additions through a supported website connection. Draft edits remain separate from the active publication.
- **Delivery reporting:** Inspect recorded Markdown responses, requester claims, verification evidence and published versions. Delivery records show what was served, not whether it appeared in an AI answer.
- **Public demo:** Try a public URL, inspect the parsed source and explore AI-drafted narrative examples. Demo results do not connect a website or publish content.

## Why trust us

### Inspect the source and understand the evidence

Optiview makes the publishing process inspectable. Teams can review parser output and a combined published-output preview, check source information, and inspect publication history before deciding what to make available.

The public demo provides a way to evaluate output using a real public page. Source access and extraction limitations remain visible; blocked or inaccessible content may be missing. A preview is not proof that a live request received the same output.

Delivery reporting distinguishes claimed requester names from available verification evidence. A verified AI category does not by itself verify a named provider. A served Markdown response is evidence of delivery, not proof of ingestion, recommendation, citation or revenue.

Learn more about the evidence and its limits at https://optiview.ai/proof/.

## Helpful knowledge

### Common questions about using Optiview

**Does Optiview replace our website or CMS?**
No. Optiview adds a publishing layer. It does not rewrite your CMS pages; normal HTML requests retain the website experience through supported connections.

**What can we add to the Narrative Graph?**
Brand descriptions, mission and audience context, products and services, supporting facts, FAQs, policies and next steps. Choose whether each item applies across the website or to one exact page.

**Does saving publish our changes?**
No. Saved edits remain in the draft. An authorized user publishes the graph to activate the reviewed content. Later edits stay separate until published again.

**Does every AI system receive Markdown?**
No. Delivery depends on the connection, request and source eligibility. Some systems explicitly request Markdown; supported delivery paths can also select it for verified AI categories. Other tools retrieve HTML and extract text themselves.

**Is Optiview an AI visibility monitoring tool?**
No. Optiview helps you improve and publish the source. Keep using your visibility tools to study AI answers; use Optiview’s delivery evidence to understand recorded serving activity.

**Does the demo save a graph to our workspace?**
No. The public demo is a separate preview. Its AI-generated proposals require review and are not automatically transferred to a workspace or published.

**Do we need a developer?**
Your web team may need to help establish and verify the connection. Once connected, authorized content users can manage narrative updates in the admin.

**Will Optiview guarantee citations?**
No. You control the source you publish. AI systems decide what to retrieve, use and cite.

## What to do next

### Try your website, then plan your connection

- [Try your website](https://optiview.ai/demo/) to inspect a public page’s parsed content and explore proposed narrative additions.
- [See how Optiview works](https://optiview.ai/how-it-works/) to understand the parser, Narrative Graph and combined publishing workflow.
- [Explore who it’s for](https://optiview.ai/partners/) if you are an agency, CMS or commerce platform, or AEO/GEO provider bringing recommendations to customers.
- [Review connection options](https://optiview.ai/web-teams/) and the [setup guide](https://optiview.ai/docs/setup/) with your web team.
- Contact [hello@optiview.ai](mailto:hello@optiview.ai) to discuss access, your website and the right setup. We provide assisted workspace setup.

Already connected? Review your Narrative Graph, publish when ready, inspect the combined output in the Markdown tab, and check recorded delivery in Activity.

[Inspect unbranded AI conversation examples](https://optiview.ai/proof/#live-evidence), including exact prompts, answer excerpts, publication versions and matching response-body hashes. The examples are selected first-party observations, with unbranded discovery and directed URL tests labeled separately; they do not establish increased recommendation frequency.