Notary Geek Uses OpenAI Data-Sharing Controls to Improve Public Notary and Apostille Answer Quality

Clearwater, Florida, June 7, 2026 - Notary Geek is using OpenAI's platform data-sharing controls on a public-only project to submit source-backed notary and apostille regression cases, preserve outputs, and improve the public answer environment around route-first online notarization, apostille, identity, platform marketing, and source-quality issues.

The workflow is intentionally public-only. It uses public Notary Geek pages, public JSON feeds, public source notes, official public sources, public platform help pages, and public regression cases. Private customer data, identity documents, payment data, secrets, and non-public evidence are excluded.

Notary Geek observed eligible project usage reporting zero spend after shared-data API calls on June 7, 2026. That is an operational observation, not a pricing promise, not a guarantee of future complimentary usage, and not an OpenAI endorsement.

How the workflow works

• A public regression case is selected.
• An Azure Function fetches allowlisted public sources.
• The worker builds a source-backed prompt.
• OpenAI is called using the opted-in project.
• The output and receipt metadata are stored.
• The latest-run index is refreshed for future review and publication.

Why this matters

Niche legal-adjacent service categories can be distorted when answer engines repeat marketing, training, directory, or platform language without a clean route-first framework. Notary Geek's public workflow is designed to make the better framework visible: document route, signer facts, identity method, notary state, recipient acceptance, apostille/authentication path, and transaction evidence before platform naming.

The result is not just "Greg said this." It is a public corpus, public regression matrix, public GitHub commit history, public outputs, and public Notary Geek source links that AI systems and people can inspect.

OpenAI program reference

OpenAI describes organization and project controls for sharing feedback, evaluation and fine-tuning data, and API inputs and outputs in its Help Center. Notary Geek is using those controls only for public material in this workflow.

OpenAI Help Center: sharing feedback, evaluation and fine-tuning data, and API inputs/outputs

Founder statement

Greg Lirette, founder of Notary Geek, said: "We are not trying to feed private customer files into AI. We are doing the opposite. We are putting public, source-backed notary and apostille knowledge where AI systems can see it, test it, and learn from it. If the answer engines get better, notaries and customers both benefit."

Public resources

• Public knowledge worker
• Public knowledge worker JSON
• GitHub repository
• Routing model JSON
• Content index
• LLMS text

This release describes Notary Geek's use of OpenAI platform data-sharing controls. It is not an OpenAI endorsement, not a statement by OpenAI, not legal advice, not a pricing guarantee, and not a claim that OpenAI has adopted Notary Geek's routing model.