Tag an AI
The Revelation Standard Social · Your key, your bill
In The Revelation Standard Social you can tag @claude, @chatgpt, @gemini or @grok in a comment, and that AI answers in the thread. Ask it what a verse means, whether a color pairing works, how a reference should be written.
It runs on your own key and is billed to you – never to us. That is not a policy, it is the only way this can exist. X can put Grok in its replies because X owns Grok. We own none of these, so the request has to be yours.
The one thing people get wrong
A ChatGPT Plus or Claude Pro subscription does not include API access. They are separate products on separate meters. Paying $20 a month for the chat app gives you nothing to paste here.
What you need is an API key, which comes from a pay‑as‑you‑go account: you put a few dollars in, and each answer draws a fraction of a cent against it. A comment‑length reply costs well under a cent. Five dollars lasts a long time.
Getting a key
All four work the same way: make an account, add a little credit, create a key, paste it into the app once.
| Claude | console.anthropic.com → Billing, add credit → API keys → Create key. Starts sk-ant- |
|---|---|
| ChatGPT | platform.openai.com → Billing, add credit (minimum $5) → API keys → Create. Starts sk- |
| Gemini | aistudio.google.com → Get API key → Create API key. Starts AIza |
| Grok | console.x.ai → add credit → API keys → Create. Starts xai- |
Leave auto‑reload off while you are finding your feet. Top up by hand and you can never be surprised by a bill.
Connecting it
- Open The Revelation Standard Social and go to the AI tab.
- Paste the key next to the AI it belongs to and tap Connect.
- In any thread, write a comment that includes
@claude(or any of the four) and your question.
The answer appears in the thread underneath, labeled with which AI wrote it and who asked. If the first mention names one AI and a later word names another, only the first answers – one question deserves one answer.
How your key is held
An API key is a live payment instrument. Ours is the strictest handling we know how to give it:
- Encrypted at rest with AES‑256‑GCM. It is never stored as readable text.
- The wrapping key is a server secret, held outside the database. A stolen copy of the database decrypts nothing on its own.
- A fresh random IV for every key. Reusing one would undermine the encryption entirely.
- Your account ID is bound into the encryption. A row copied to another account fails to decrypt rather than quietly working.
- It is never sent back to any app, never written to a log, never placed in a web address. The only part that ever leaves our server again is the last four characters, so you can tell which key you saved.
- Delete it whenever you want, from the same screen. Deleting your account deletes it too.
You can also revoke the key at the provider at any moment, which cuts it off no matter what anyone holds.
What the AI can see
Only the design being discussed – its scripture reference, color, garment and font – plus the words of your own comment. It is not given your email, your orders, your address, or anyone else’s comments.
Rules it answers under
An AI answer is attributed to the AI but tied to the account that asked for it. It can be reported, hidden and appealed exactly like anything a person wrote. Nobody gets to hide behind a machine.
Cost, plainly
You pay your AI provider directly, at their rates. We take nothing and add nothing. If your balance runs out the AI simply says so, in its own words, and your comment still posts.
Why not Copilot or Meta AI
Neither offers a public API a person can get a key for. Listing them would be a button that could never work, so they are not listed.
Questions
Email FounderandCEO@TheRevelationStandard.Com. A real person answers.
← Back to The Revelation Standard