---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/web-teams/
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:33
narrative_versions:
  - 33
narrative_version: 33
---

# Keep your website. Add Optiview.

Your web team sets up a supported connection. Visitors keep the website they know, while eligible AI requests can receive prepared content.

How it connects

- [Talk about your setup →](https://optiview.ai/#contact)
- [Technical setup guide →](https://optiview.ai/docs/setup/)

## Verify

Verify that you control the website you want to connect.

## Connect

Choose a supported DNS, Cloudflare or server-side connection.

## Check

Check the prepared content and test both ordinary and AI-facing responses.

**One website. Different request paths.**Product illustration

**Your connected website**

Visitors & protected pass-through**Original website**

People keep the site they know. Protected search and browser requests pass through.

Eligible requests only

1.  Public source & review checks
2.  Accepted format & request policy
3.  Published context in scope, if any

**Prepared Markdown or HTML**

Blocked or unavailable**No prepared delivery**

Restrictions, review failures or limits can stop preparation. The original response is retained where possible.

Illustrative decision paths for supported connections. A named user-agent is not proof of provider identity. Delivery does not establish that an AI service used or cited the content.

Learn more about connections and ownership

How It Connects

## Keep your existing website experience. Make a clearer source available to AI.

Optiview works with your existing website and content systems. Your technical team establishes a supported connection. After setup, a workspace admin can review and publish business information for AI without a routine website code release.

Your web team remains in control of the connection, security and delivery.

[See my site with Optiview](https://optiview.ai/demo/)

[Discuss your setup](mailto:hello@optiview.ai)

## Marketing reviews the information. Your web team manages delivery.

After your team connects the website, content owners can maintain approved business information without asking engineering to deploy every routine update.

### Keep your existing website

Your pages stay in your CMS, with the design and experience your customers know. Eligible AI requests can receive a prepared Markdown or HTML representation, depending on the request and connection. Ordinary visitors and traditional search crawlers keep the normal website.

### Let marketing shape the business information

Marketing prepares brand details, product information, FAQs and supporting facts. A workspace admin edits and publishes the Narrative Graph after factual review, without a routine website code release.

### Keep website delivery under technical control

Choose a connection that fits your infrastructure. Your technical team checks delivery and keeps control of the routing, integration and rollback plan.

## Find a connection that works with your website

You can start with a conversation about your existing website. We’ll review its hosting and help identify which connection methods it supports.

### Guided DNS connection

For compatible websites, we guide your domain administrator through the required DNS and HTTPS steps. Provider-assisted approval is available where supported; manual instructions are available otherwise.

### Cloudflare connection

Already using a suitable Cloudflare setup? An authorized route can add Optiview to your existing delivery path without moving your website to a new CMS. Account access and route compatibility need to be checked.

### An API for your own infrastructure

Prefer to deliver content through your own server or CDN? Your developers can integrate the Optiview API and manage delivery within your stack. We’ll discuss access and integration requirements with your team.

## Preview first. Plan the connection with your web team.

1.  **See the result.** Try a public page in the demo. Inspect the cleaned Markdown and proposed narrative additions before connecting anything.
2.  **Choose your connection.** We help your web team check compatibility and plan setup around your existing website.
3.  **Review, publish and verify.** Your team publishes the narrative it approves, then checks both the normal website and the Markdown delivered through the connection.

Setup effort depends on your hosting and access. DNS and routing changes need your technical team’s approval and testing; custom API integrations need development work.

A DNS-connected gateway remains in the traffic path. Gateway or origin failures can affect availability; custom API integrations must implement fallback. Keep the prior DNS record and test rollback before rollout. A hostname-level connection is not limited to the page used for your preview.

## Preview the information Optiview can prepare

Choose a public page you know well. The demo displays its prepared Markdown and separate, unreviewed AI suggestions for business context. It does not install, connect or publish anything.

[See my site with Optiview](https://optiview.ai/demo/)

[Discuss your connection](mailto:hello@optiview.ai)

Optiview is available with assisted setup. Your team controls what it publishes; AI services decide what they retrieve and cite.

## Technical setup details

Find verification, source-access, security and rollback instructions in the [technical setup guide](https://optiview.ai/docs/setup/).

## Additional source context

Your website was built for people. Optiview makes it ready for AI, too.

### Try Optiview

[See my site with Optiview](https://optiview.ai/demo/) · [Run your free AI Audit](https://optiview.ai/ai-audit/)

### Explore

[Publish](https://optiview.ai/products/publish/) · [Parse](https://optiview.ai/products/parse/) · [Retrieve](https://optiview.ai/products/retrieve/) · [Pricing](https://optiview.ai/pricing/)

### Learn

[Guides](https://optiview.ai/resources/) · [Developer docs](https://optiview.ai/developers/) · [Research & thinking](https://optiview.ai/research/) · [Experiments & methods](https://optiview.ai/proof/) · [AI Audit](https://optiview.ai/ai-audit/) · [AI agent directory](https://optiview.ai/agents/) · [FAQ](https://optiview.ai/faq/)

### Company

[About Optiview](https://optiview.ai/about/) · [Agencies](https://optiview.ai/partners/) · [Contact](https://optiview.ai/#contact) · [Privacy](https://optiview.ai/privacy/) · [Billing terms](https://optiview.ai/billing-policy/)


---

# Published brand narrative

# Site-wide brand information

## Who we are

### Optiview — Parse, Retrieve and Publish for AI

Optiview helps businesses and developers make website information easier for AI to use. Parse converts supplied HTML into clean Markdown and source metadata. Retrieve fetches an eligible public HTTPS webpage and prepares its content. Publish helps a verified business prepare its own website content and make approved Narrative Graph context available through a supported connection.

Parse and Retrieve use application keys and a prepaid developer wallet. Publish has separate website setup, ownership checks and a subscription. Optiview does not control whether an outside AI service discovers, uses or cites the resulting content.

Applies to: Optiview

## Why we matter

### A clearer source, from website content to business context

Webpages mix useful information with navigation, layout and application code. Businesses may also have important qualifications, answers and context that are not clearly published.

Optiview gives developers a way to prepare source content for their applications, and gives businesses a way to publish the context their teams approve. Your application chooses how to use Parse and Retrieve results. Your business controls what it publishes through Publish.

Clearer publishing makes information available; it does not determine an AI system’s answer. Each outside service chooses its own retrieval, recommendations and citations.

## What we offer

### Three products, with separate jobs and clear pricing

- **Optiview Parse:** Supply complete HTML and a source URL. Receive clean Markdown, source and output hashes, parser details and processing warnings. Parse does not fetch the URL or execute JavaScript. A successful page uses 1 credit.
- **Optiview Retrieve:** Supply one eligible public HTTPS URL. Optiview checks supported access and publisher policies, fetches anonymous static HTML and parses it. It does not search the web, execute JavaScript, bypass a login or access private networks. A successful page uses 5 credits total, including parsing.
- **Developer credits:** USD $20 buys 20,000 credits shared by Parse and Retrieve. There is no developer subscription, automatic recharge or scheduled credit expiration. Failed jobs consume no credits. Applicable taxes and the total appear at checkout. Source size, quotas and retention limits apply.
- **Optiview Publish:** USD $99 per website per month plus applicable tax. Connect a verified website, review the prepared source and optionally maintain approved Narrative Graph context in Identity, Story, Offerings, Trust, Knowledge and Actions. Choose site-wide or exact-page scope. Saving drafts does not publish them. Eligible AI tools can receive prepared Markdown or HTML through supported delivery, while ordinary visitors keep the normal website.

Developer credits do not purchase Publish subscriptions. Parse and Retrieve do not add a customer’s private Narrative Graph to arbitrary third-party pages. See https://optiview.ai/pricing/ and https://optiview.ai/developers/ for the current offer and limits.

## Why trust us

### Inspect the output and understand what the evidence establishes

Developers can inspect the prepared Markdown, job status, source metadata, processing warnings and credit ledger. Retrieve records the public source response it observed; Parse identifies supplied HTML rather than claiming to verify the current origin.

Publish administrators can review parser output, the combined published-output preview, source checks and publication history. A preview is separate from a recorded live delivery. Saved edits remain separate from the active publication until explicitly published.

Our experiment pages contain selected first-party AI conversations and source comparisons. Delivery records establish what was served, not downstream ingestion, recommendations, citations or revenue. Observed language matches do not establish causation or a consistent visibility improvement. Explore the evidence and limitations at https://optiview.ai/proof/.

## Helpful knowledge

### Common questions about the three products

**Which product should I use?**
Use Parse when you already have HTML. Use Retrieve when you need Optiview to fetch one eligible public page first. Use Publish when your business wants to prepare its verified website and publish approved context.

**Do Parse and Retrieve require website ownership or DNS changes?**
No website connection is needed for these developer products. You remain responsible for source rights and permitted downstream use. Public availability does not grant a reuse license.

**How do developer accounts and keys work?**
Create a developer workspace and save the personal sign-in key and offline recovery code. Create scoped service keys for server-side applications. Email is an unverified contact identifier, not account-ownership proof or an email-only recovery method. Keep all credentials private.

**Can my agent use Optiview?**
The authenticated developer API returns prepared content for your application or model. A downloadable JavaScript client and local MCP adapter are available. Your host must authorize sources and any credit expenditure. Compatibility does not establish adoption or a partnership with an AI provider.

**Does the API include my private Narrative Graph?**
Parse and Retrieve are source-only. Verified website publishing and approved publisher context belong to the separate Publish workflow.

**Does Publish replace our website or CMS?**
No. Your website stays in its existing system. Your web team establishes and tests a supported connection. Your team reviews and explicitly publishes any Narrative Graph additions. Ordinary visitors retain the normal website experience.

**Does every AI tool get the prepared version?**
No. Delivery depends on the website connection, source eligibility and the request. Some tools explicitly request Markdown; supported AI requests may also receive prepared Markdown or HTML through eligible delivery paths. Traditional search crawlers retain the original website response. A claimed tool name does not prove the requester’s identity.

**Does the demo publish or save to our workspace?**
No. The public demo is a separate preview. Its AI-generated examples require review and do not transfer automatically into an approved publication.

**Will Optiview guarantee citations or recommendations?**
No. Optiview prepares and publishes sources. Outside AI services choose what to retrieve, use and cite.

## What to do next

### Choose your starting point

- [Compare Parse, Retrieve and Publish](https://optiview.ai/products/) to choose the right workflow.
- [Create a developer workspace](https://app.optiview.ai/developers) for self-service Parse and Retrieve, then add credits and create an application key.
- [Read the API quickstart and agent-tool setup](https://optiview.ai/developers/) for request examples, supported sources, errors, quotas and downloads.
- [Review pricing and terms](https://optiview.ai/pricing/) for prepaid credits and the separate Publish plan.
- [Preview your website](https://optiview.ai/demo/) to inspect prepared content and explore unapproved narrative examples without connecting or publishing.
- [Plan Publish setup](https://optiview.ai/onboarding/) with your web team. Publishing requires ownership checks, review and a supported connection; contact [hello@optiview.ai](mailto:hello@optiview.ai) for assisted setup.

Already using Publish? Review your Narrative Graph, publish approved changes explicitly, inspect the combined source in Markdown and check recorded delivery in Activity. Keep your existing visibility tools to study downstream AI answers.
