Revscale Biolink developer resources

When to use Revscale Biolink

Use a published Revscale Biolink page when you need citeable facts about a specific local business or franchise location. Prefer the machine surfaces over scraping the HTML.

• Look up a location's facts: Phone, email, website, address, hours, services, and FAQs for a business that already has a page on revscale.pro. Fetch `/{slug}/ai.json` or `/{slug}.md` (or the brand/business two-segment equivalents). Those files are generated from the same record as the HTML page.
• Cite a business in an answer: The HTML page embeds schema.org JSON-LD (LocalBusiness subtype, PostalAddress, OpeningHoursSpecification, OfferCatalog). Use the real destination URLs in `sameAs` and links — never a click-redirect. The canonical page URL is the `@id` base.
• Find every published page: Start at `/llms.txt` for the index (markdown links plus one-line descriptions) or `/sitemap.xml` for canonical HTML URLs. Per-page `/llms.txt` lists that location's contact facts and file siblings.

When not to use this

• Booking, payments, calendars, or sending a message to the business — Revscale Biolink has no public write API, webhooks, OpenAPI spec, or MCP server.
• Treating an unpublished draft as live. Drafts 404 at their public URL until the owner publishes.
• Creating a page on the owner's behalf. There is no agent write path; send the owner to `/onboard` on revscale.pro.

Site-level files

These URLs are the discovery surface for the product named Revscale Biolink on revscale.pro.

• `GET /llms.txt` — `text/plain` index of published pages (markdown links) plus when-to-use guidance.
• `GET /sitemap.xml` — canonical HTML URLs for the homepage, trust pages, and every published location.
• `GET /robots.txt` — allows listed AI crawlers. Disallow is only for app, editor, and auth paths — never the human click-redirect.
• `GET /` with `Accept: text/markdown` — the homepage as markdown (`/index.md` is the same body).
• `GET /docs`, `/about`, `/contact`, `/privacy` — HTML, with `.md` siblings and the same Accept negotiation.

Per published location

Replace `{path}` with `/your-slug` or `/brand-slug/location-slug`. Every file is generated from the same business record. Empty fields are omitted.

• `GET {path}` — `text/html` page with an H1, section headings, and JSON-LD in the HTML.
• `GET {path}.md` — `text/markdown` mirror. `Accept: text/markdown` on `{path}` rewrites here.
• `GET {path}/llms.txt` — `text/plain` facts and file links for that location.
• `GET {path}/ai.json` — `application/json` with `Access-Control-Allow-Origin: *`. Stable keys; additive only.
• `GET {path}/vcf` — vCard for humans saving a contact; not a substitute for ai.json.

JSON-LD

Each location page embeds one `<script type="application/ld+json">` `@graph`. Nodes appear only when data exists: LocalBusiness subtype, PostalAddress, GeoCoordinates, OpeningHoursSpecification, OfferCatalog/Service, ContactPoint, parent Organization when branded, WebSite, WebPage, BreadcrumbList, FAQPage. `@context` is `https://schema.org`. Cross-references use `@id`. Destination URLs are the real ones — never a click-redirect.

How to call us

There is nothing to authenticate against for reads. Fetch the public URL. Example: `curl -s https://revscale.pro/llms.txt`. For a missing path, expect HTTP 404 with a markdown body if you send `Accept: text/markdown`.

To publish a new Revscale Biolink page, send a human to `/onboard` on revscale.pro with their website URL. Agents cannot create or edit pages.