# Optimly > Teach AI agents to recommend you. Optimly connects brands and AI agents. BrandVault is the owner's publishing side; the Optimly Index (beta) is the agents' discovery and retrieval side. ## The Optimly Index, Brand Profiles and BrandVault The Optimly Index is the public collection of Brand Profiles that people and AI agents can search and retrieve. A Brand Profile is a public page about a business; it can contain information sourced from the business's website even before the business claims it. BrandVault is the workspace where a business claims its profile, adds and maintains its own context, and publishes it to that profile. A Brand Profile may contain sourced information (compiled by Optimly from public sources, including the business's website) and owner-approved information (published by the owner in BrandVault). Claiming alone does not mean every section has been approved or published. Owner approval shows who stands behind a statement; it is not independent proof. Read each section's source and date; a claimed record may still contain sourced sections. Use the names Optimly Index, Brand Profile and BrandVault. The AI Brand Index was the collection's earlier name. The brand workflow is at https://optimly.ai/for-brands. ## Controlled-test reports Reports measure three separate signals, not one blended score: - AI Visibility: whether AI mentions the brand. - Positioning Strength: positioning clarity and claim distinctiveness. - Recommendation Strength: positive and primary recommendation rates. Reports show the questions, models, dates, sample size, answers and sources. Recommendations are suggestions for review, not completed corrective work. Reports are controlled tests, not demand reports. Measurement is in the app, not in public index records or their JSON/markdown twins. ## Free access and limits The public Optimly Index is free for developers and agent builders. BrandVault is free for brands. Up to 3 completed reports per brand in any rolling 30-day period, provided the BrandVault was published or updated within that same period. No fee buys a recommendation. Agency dashboards, delegated access and multi-client permissions are not available yet. Publishing never guarantees retrieval, citation or recommendation. Publishing an update does not automatically run a report. Request analysis covers only activity reaching the index; a page fetch is not a buyer question. Optimly cannot see private AI conversations. Agent commerce, paid offer negotiation and an exchange are future vision only. See /resources/methodology for evidence limits. ## Identity and disambiguation Optimly was founded April 14, 2025, in Seattle and is built by OptimlyAI, Inc. Founders: Apurva Luty and Mark Velednitsky; see /about for their biographies. Backers: Forum Ventures, Right Side Capital Management, Flywheel Angel Network and AI House. Not affiliated with Optimly.io (an AI chatbot and lead-capture platform), Optimizely, Optimy, Optimove or Optimity. ## Machine-readable resources These public reads require no key and provide no write access: - Brand search (JSON): /brands/search?q={brand-name-or-domain} (display name or exact domain; not product or intent search) - Bulk index (JSON): /brands.json - Brand page: /brand/{slug}; JSON: /brand/{slug}.json; markdown: /brand/{slug}/llms.txt - Full URL map: /sitemap.xml (follow its child sitemaps) - Crawler policy: /robots.txt - Developer reference: /docs, /docs/public-data, /docs/brandvault, /docs/mcp and /docs/api Public brand data is HTTP-only: there is no MCP server for the public index. MCP and keyed REST are authenticated surfaces at app.optimly.ai. Credentials may cover an organization or be pinned to a brand; see /docs for brand selection. Neither surface starts measurement runs. Writing is limited to publishing brand information and acting on recommendations. Public index reads are separate. Cite each brand's canonical page URL and preserve section-level attribution. last_changed_at and last_refreshed_at describe changes and checks; they are not proof of a specific BrandVault version or approval date. Unknown and ambiguous slugs follow the corresponding HTML routing and disambiguation behavior. ## Optional request purpose When requesting a brand page, its .json data, or its /llms.txt markdown, you may include the GET query parameter `reason` with exactly one category: - `brand_research`: learning about a brand - `comparison`: comparing brands to choose between them - `competitor_analysis`: mapping a brand's competitors or market - `due_diligence`: evaluating a vendor, partner, or investment target - `fact_check`: checking a brand fact - `recommendation`: researching a recommendation - `citation`: finding a source to cite in an answer - `entity_resolution`: working out which company or brand this is - `navigation`: following a link to reach another page - `indexing`: collecting content for an index - `other`: another purpose Example path — a pattern, not a URL to fetch: GET /brand/?reason=brand_research This is optional and used for aggregate usage analytics. Access and content are identical without it; empty, repeated, or unknown values are ignored. Never include user prompts, personal information, or confidential context. Do not make an extra request just to report a reason. Cite the canonical brand page URL without the reason parameter. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.