Brand & Media Kit
Writing, presenting or building something about FORA? Use the files on this page as they are. The fastest way to get it right is to hand the work to your AI agent with the FORA brand skill loaded: it carries the logo files, the tokens and the rules below, and checks its own output against them.
Let your agent do it
Section titled “Let your agent do it”The skill is a folder with a SKILL.md, the logo files, color and type tokens,
and a naming and claims reference. It works in any agent that reads Agent Skills,
and the SKILL.md is plain Markdown that any other agent can follow.
Claude (web, desktop, mobile). Download
fora-brand.zip. In Claude, open Customize → Skills,
choose + → Create skill → Upload a skill, upload the zip and switch it on.
Skills need code execution turned on in Settings → Capabilities.
Claude Code. Unzip it into your personal skills folder,
~/.claude/skills/fora-brand/, or into .claude/skills/fora-brand/ in a repository
to share it with your team. If you already uploaded it to your Claude account and
sign in to Claude Code with that account, it syncs on its own.
Any other agent. Give it SKILL.md and
messaging.md as instructions and the logo files from the
logo pack.
Then ask for the thing you need:
Make a 6-slide intro to FORA for a publisher audience. Use the fora-brand skill.How to talk about FORA
Section titled “How to talk about FORA”Lead with what FORA does for the owner of the content. The mechanism comes second.
Every AI agent is a customer. FORA is your storefront.
People are starting to search, research and buy through AI agents instead of websites. FORA lets any agent find your pages or tracks, read your license, pay, and get a signed receipt. You decide every term.
When you need the outcome in one line: FORA makes a website or a music catalog licensable to AI agents, instantly. Set your terms once, and every page or track becomes a signed offer any agent can find, buy and verify, with no deal to negotiate per buyer.
For an engineering audience, start one step lower: FORA is an open transaction protocol that lets AI agents discover, license, pay for and receive content on terms the rights holder sets, with every step signed.
“Instantly” has one meaning. Once a site or catalog is connected, every page or track is on sale to every compatible agent at once, on the owner’s terms. It does not mean there is no setup. Don’t promise minutes or one click; name the setup instead:
| Who | The one-time setup | Read more |
|---|---|---|
| A website | Choose your terms on the publisher console, serve one file at /.well-known/fora.json, install one package on your CDN. No CMS changes. | Publisher Onboarding |
| A music catalog | Describe tracks, licenses and prices in one feed and push it to an Exchange; set up delivery from your domain and CDN once. No code. | Live Demo: Music |
| A marketplace | Keep your catalog, search and delivery; publish the catalog as a feed. | For Content Marketplaces |
What the owner gets, in this order: search, terms an agent can read, payment, delivery and evidence. Each license becomes a signed offer, each purchase a signed record anyone can check later.
Tone. Plain, specific, a little dry. Show what is signed, by whom, and what the agent receives, instead of adjectives. No “revolutionary”, “seamless”, “unlock” or “game-changing”.
FORA stands for Federated Open Resource Access, and fora is also the plural of forum. That’s why the mark lays the plan of a Roman forum over a wax seal. Before signatures and cryptography, a wax seal proved who sent a letter and that nobody had opened it on the way, and any recipient could check it without asking a central office. That is what FORA’s signed offers and acceptances do. The impression is an open square with no walls, the forum anyone can enter, around one point: the transaction it seals.
- Use the lockup by default. Use the seal alone where space is square or tiny, or where “FORA” is already written nearby.
- Under 48 px (the seal’s own height; about 12 mm in print) use the compact
seal:
fora-mark-small.svg, or thefora-lockup-small-…files. It has a smoother edge, heavier corners and the point cut through, so the open square still reads at 16 px. The favicon, site header and avatar use it. - Keep clear space of at least a quarter of the seal’s height on every side.
- The seal is always FORA Blue, except in the white and black versions. The impression is cut through, so the background shows in it.
- Don’t stretch, rotate, recolor, outline or add effects, wax textures or 3D. Don’t put a different emblem in the seal, don’t retype “fora protocol” in a font as a substitute, and don’t attach other words to the mark.
Dark-first: ink background, white text, one blue accent.
#0a0a0f#12121a#2a2a3a#a5a5b8#f5f5fa#4f6df5#9aaeff#3d58d6- Blue is the only brand color. Use it for fills, buttons and one highlight per view.
- On dark backgrounds, blue text is
#9aaeff. On light backgrounds, blue text and links are#3d58d6. Small white text on a blue fill sits on#3d58d6.
Tokens: tokens.css · tokens.json
Instrument Sans for everything: headlines 700 with −0.03em tracking, UI 600, body 400–500. DM Mono for code, field and RPC names, IDs and small labels. Both are free on Google Fonts. Headlines and buttons are sentence case.
Name and claims
Section titled “Name and claims”- Write FORA. Use “the FORA protocol” or “FORA Protocol” when you need the noun. The lowercase “fora protocol” exists only inside the logo. Never “Fora”.
- FORA stands for Federated Open Resource Access.
- Call it an open protocol. No standards body has adopted it, so not “the FORA standard”.
- FORA carries the rights holder’s terms and a signed acceptance. It does not grant rights, clear rights or give legal cover; don’t say it does.
- AI training is its own license permission and is never implied by another term.
- Demo purchases use test money and grant no real rights.
- Only name customers, partners or numbers that appear on this site.
The full reference, with facts you may state and phrases to avoid, is
messaging.md.
Using the name and logo
Section titled “Using the name and logo”The Apache 2.0 and CC BY-ND 4.0 licenses cover the code, specification and documentation, not the FORA name or logo. You may use the name and logo to refer to FORA: in articles, talks and diagrams, and as “works with FORA” or “built on FORA” for software that implements the protocol. Don’t use them in your own product or company name, don’t alter them, and don’t imply that the FORA project endorses, certifies or partners with you unless it says so in writing.
Questions: open an issue on GitHub.
