Platinum
Summary
AI agents crawling vendor sites have a budget — measured in tokens — and when your pricing lives in a JavaScript-rendered table or your hours are buried in an image, agents skip you for whoever is cheaper to read.
Platinum.ai generates an llms.txt profile for your business: a machine-readable file, formatted to the open llms.txt standard, that sits on your domain and hands agents your services, pricing, hours, and policies in under 600 tokens instead of requiring a full page scrape. The vendor states profiles are built using over 150 industry-specific blueprints, so the fields agents look for when evaluating a dental clinic differ from those for a law firm. You upload one file — no code changes, no redesign, no plugin. The ceiling appears quickly: this is a static document, so anything that changes on your site requires a manual update or a return purchase. Teams with fast-moving pricing or rotating service lines will find the file stale within weeks.
Bottom line: The right call for a local service business whose facts are stable and whose site is invisible to agent crawlers — a poor fit for any operation where pricing or offerings shift faster than you will remember to update a background text file.
Pricing Plans
- Price
- From $99 one-time
Core
Basic AI Website Profile
Complete
Enhanced AI Website Profile
View full pricing on platinum.ai →
Pricing may have changed since last verified. Check the official site for current plans.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Delivers a machine-readable llms.txt file in the open standard format agents already look for, which means agents retrieving your domain get structured facts in under 600 tokens rather than burning budget on a JavaScript-heavy scrape that may still return wrong data.
- Over 150 industry-specific blueprints shape which facts get prioritized, so a dental clinic's profile surfaces credentialing and insurance fields that a generic summary would omit — the data agents actually weight when comparing providers in that category.
- One-time delivery with no plugin installation or site redesign required, which means your existing site architecture is untouched and there is no recurring dependency to manage or cancel.
- Puts your business in control of the facts agents cite about you, replacing the current default — scraped directories, cached reviews, outdated listings — with a source you authored and can correct.
Cons
Sign in to edit- The profile is a static file with no automated sync to your live site — the moment your pricing, hours, or services change, agents reading your llms.txt will retrieve stale facts, recreating the misinformation problem the service is sold to prevent. Teams with any price volatility will need to repurchase or manually maintain the file.
- There is no API, no CMS integration, and no described webhook or trigger mechanism, which means businesses that update offerings frequently have no path to keeping the file current short of manual intervention every time something changes.
- Because the output is a text file with no performance tracking, there is no signal telling you whether agents are actually reading it, which queries it is answering, or whether it is affecting how often your business appears in agent-driven comparisons — teams that need attribution data will find nothing here and move to structured schema implementations with analytics hooks instead.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- API Available
- No
- Self-Hosted
- No
- Last Updated
- 2026-06-19T21:11:17.704Z
Best For
Who it's for
- Local service businesses
- Professional service providers
- Any company wanting agents to read their site first
What it does well
- Make business facts machine-readable for AI agents comparing vendors
- Ensure correct pricing, hours, and services appear in agent outputs
- Prioritize a site in agent crawling over competitors without structured profiles
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare Platinum
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Platinum free?
- Platinum is a paid tool (From $99 one-time). No permanent free tier is offered.
- Is Platinum open source?
- No — Platinum is a closed-source tool. Source code is not publicly available.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Agents crawling the web to compare vendors are not reading your site the way a person does — they are parsing structured text under a token budget, and sites that cost too much to interpret get dropped from the shortlist before a human ever sees the result. Platinum.ai addresses this by building what the vendor calls an AI Website Profile: a single llms.txt file that encodes your business facts — services, pricing, hours, contact details, policies — in the exact format agents expect, then sits quietly at your domain root so any crawling agent retrieves a clean briefing instantly.
The differentiating claim is industry specificity. Rather than outputting a generic text summary, the vendor states they use over 150 industry-specific blueprints that front-load the fields agents weight most heavily for your category — credentialing for law firms, covers and reservation policies for restaurants, security posture for IT consultants. The profile is built by the Platinum.ai team after reviewing your existing site, then delivered as a file you add to your server. No redesign, no ongoing subscription is required.
This model fits businesses with stable, well-defined facts: hours that do not change weekly, a service menu that holds for months, pricing that is not quote-dependent. Where it breaks is equally specific: the file is static. If your rates change, your llms.txt does not update itself. Agents querying your domain after a price change will read the old number — the same misinformation problem the service exists to solve, now owned by you instead of a scraper. There is no API, no self-hosted option, and no described mechanism for automated re-generation when your source site changes.