Our own site, through the API

From submission to technical receipt

1. 01

   Submit

   POST /audits accepted our original hosted deployment with HTTP 202 and a persistent audit ID.

2. 02

   Process

   The locally invoked, authenticated processor completed the queued audit using the shared audit engine.

3. 03

   Read back

   GET /audits/{id} returned HTTP 200, status completed, the score, findings and saved fix draft.

Six check groups, one score

What the engine observed

All @types: Organization, ContactPoint, WebSite, FAQPage, Question, Answer
Organization: complete
WebSite: complete
FAQPage: complete

Organization "AI-Primed" has no sameAs

The schema-types finding is an observation of existing markup, not a missing-schema failure. The remaining identity gap is the absence of sameAs links.

The fix returned—and why it stays a draft

schema.jsonld · Organization schema

The API saved an Organization schema draft with replacement fields for public profiles, contact details and a logo. Existing Organization markup was already complete; the draft still needs review and merging, not blind replacement.

We do not have verified public company profiles to supply for sameAs. We left that finding open rather than inventing links. There is no after-fix observation for this API test, no measured score uplift and no evidence of a change in AI mentions.

A readable extract of the response

Selected public fields from the recorded response. Account data and identifiers are omitted; this is not the full export.

{
  "schema": "agentready.audit/v1",
  "audit": {
    "site": "AI-Primed’s original hosted deployment",
    "status": "completed",
    "score": 99,
    "grade": "A",
    "completed_at": "2026-10-20T22:07:49.996034Z"
  },
  "findings": [
    {
      "title": "Detected schema.org types",
      "severity": "low"
    },
    {
      "title": "Organization has no sameAs links",
      "severity": "low"
    }
  ],
  "fixes": [
    {
      "title": "Organization schema",
      "filename": "schema.jsonld",
      "fix_type": "json_ld"
    }
  ]
}

What an integration can take from this

A visibility product can display the dated score, show the observed identity gap and offer the saved schema draft for customer review. The API supplies technical evidence and remediation output; it does not supply a new AI mention measurement or silently modify the customer’s site.

In a separate keyed audit on 20 October 2026, we compared the API result with the dashboard JSON export. The schema, audit, findings, fixes and evidence matched exactly: 99/100, grade A, two findings and one fix. This verifies the shared report contract, not deployment or third-party integration.

For prospective evaluators at Otterly, Peec or another AI visibility tool, this first-party case study is an inspectable example—not a claim that any of those tools has integrated AI-Primed.