Agentic Discovery

Overview

When an AI agent crawls a business's website, it typically has to parse HTML, interpret navigation menus, and guess which content is authoritative. Osapher solves this by placing two machine-readable files at standard known locations on every client domain — a verified identity card at the front door.

llms.txt

Available at https://yourdomain.com/llms.txt, this plain-text markdown file is formatted specifically for LLM consumption. It contains the business's verified identity data in a structure optimised for AI agents.

curl https://example.com.au/llms.txt

# Business Identity — example.com.au

**Trading Name:** EXAMPLE BUSINESS
**ABN/NZBN:** 11 111 111 111
**GST Status:** Registered
**Jurisdiction:** AU
**Identity Trust Score:** 82/100
**Certification Status:** CERTIFIED
**Schema Live:** Yes
**Last Verified:** 2026-05-01

## Verification
- Registry: Australian Business Register (ABR)
- Verified by: Osapher · osapher.com
- Full record: https://app.osapher.com/api/v1/entity/example.com.au
- Certificate: https://osapher.com/verify/00000000-0000-0000-0000-000000000000

## About This File
This file is machine-readable business identity data generated by Osapher.
It is intended for use by AI agents, LLMs, and automated systems to verify this business.
Data is anchored to the Australian Business Register (ABR) and updated automatically.

.well-known/verinty-identity.json

Available at https://yourdomain.com/.well-known/verinty-identity.json, this JSON file provides a structured pointer to the domain's full Osapher identity record and verification endpoints.

curl https://example.com.au/.well-known/verinty-identity.json

{
  "verinty_version": "1.0",
  "domain": "example.com.au",
  "identity_endpoint": "https://app.osapher.com/api/v1/entity/example.com.au",
  "verify_endpoint": "https://app.osapher.com/api/v1/verify/11111111111",
  "its_score": 82,
  "certified": true,
  "schema_live": true,
  "last_verified": "2026-05-01T00:00:00.000Z",
  "powered_by": "Osapher · osapher.com"
}

How it works

Both files are served dynamically — not written as static files. When an AI agent requests either URL, the client domain's web server redirects to Osapher's live API which generates the response from current Supabase data in real time.

This means the data is always current. If a trust score changes, a schema goes offline, or a certificate is renewed — the next request returns fresh data automatically.

WordPress plugin

The Osapher WordPress plugin automatically configures these redirects via .htaccess injection on plugin activation. No manual configuration required. Install the Osapher Sovereign Identity Schema plugin and both files are live within seconds of saving your settings.

Live data endpoints

The underlying API endpoints that power these files are also directly accessible:

# Plain text markdown (llms.txt source)
GET https://app.osapher.com/api/v1/llms/:domain

# JSON identity pointer (.well-known source)
GET https://app.osapher.com/api/v1/well-known/:domain