One source of truth your team and every AI agent can trust.
getctx is the canonical place agents fetch context — your brand voice, team docs, working style, project state. Publish once. Every agent, every tool, every teammate stays in sync.
Free to start. No card. You control what's public and what stays internal.
✓ Private by tier
✓ MCP-native
✓ On-chain verifiable
✓ Bring your own agents
THE PROBLEM
Every AI agent is working from a different version of the truth.
Brand guidelines live in a Notion page nobody opens. Positioning is in a Google Doc from last quarter. Team decisions get re-litigated every Monday. And every agent — internal or customer-facing — picks up a different fragment.
BRAND
× "Our customer service AI just told a prospect about a feature we deprecated six months ago."
— A marketing director, every week
TEAM
× "Sales AI says we ship Tuesdays. Support AI says we ship Thursdays. We ship Wednesdays."
— Your ops lead, watching the agents disagree in real time
PERSONAL
× "Chris is a product manager at..."
— ChatGPT, two years after you became CTO
THE FIX
One source. One update. Shared by every agent.
getctx is the canonical context endpoint for any entity — your business, your brand, your team, or yourself. Internal context stays private to authorized agents. Public context is open to the web.
HOW AGENTS USE IT
Here's what an agent sees when it queries your brand.
One REST call, formatted for the consumer. Ask for ?format=md and an LLM gets markdown ready to read. Ask for ?format=json and your integration gets structured data. Same source. Same truth.
$ curl 'https://getctx.ai/getctx?format=md&key=branding'
# getctx
**Branding**: # Brand voice — getctx
"The canonical context layer for AI." Tone is direct, technical without
jargon, outcome-led. Lead with the value, then the mechanism. Short
sentences. Concrete examples.
NEVER use: synergy, leverage (as a verb), best-in-class, "AI-powered,"
"revolutionize," "next-gen," "game-changer."
ALWAYS write the brand name as: getctx (lowercase, no space)
# Brand colors
- #0d5c5a deep teal — primary, accent, eyebrows
- #fafaf7 warm off-white — page background
- #0a0a0a near-black — body text
- #5a5a52 muted — secondary text
- #e6e3da warm gray — borders and dividers
# Positioning
The canonical place AI agents fetch context. One source. One update.
Shared by every agent.
# Current launch
v1 homepage — May 2026. Lead with "team and every AI agent." Brand /
team / personal in that order of emphasis.WHAT THE CONTENT AGENT NOW WRITES
Stop letting AI agents guess. getctx is the canonical place agents fetch context — one source, one update, shared by every tool. Built for teams that ship without re-briefing the model every week.
On-brand without anyone re-briefing the model. When marketing updates the voice tomorrow, every agent picks up the new line on the next query.
SETUP
From zero to canonical in three steps.
01. Claim a handle
Pick one for your company, your brand, your team — or yourself. getctx.ai/acme becomes your canonical endpoint.
02. Publish context
Brand voice, team docs, project state, working style. Tag each item public, key-guarded, or OAuth-protected.
03. Agents query it
Wire MCP clients or REST consumers to your endpoint. Update once — every agent stays in sync on the next call.
USE CASES
One pattern. Many contexts.
TEAM
Shared org context
Project state, decisions log, working agreements. Every internal agent — and every teammate — queries the same source. No more drift between humans and tools.
BRAND · MOST POPULAR
Brand voice, locked in for every agent
Positioning, tone, do's and don'ts, current launch. Every AI agent your team or clients use stays on-brand by default. Update marketing's source of truth, and the customer service bot is on-message by the next query.
PERSONAL
Your context, your way
Skills, working style, expertise, projects in flight. AI tools stop guessing about you and start asking the right questions.
BUILT FOR TRUST
Private by default. Verifiable by design.
Tiered access
Public, key-guarded, OAuth, escrowed. Set per item — internal context stays internal.
On-chain verifiable
Every item hash-anchored. Customers and partners verify integrity without trusting us.
Encrypted at rest
Raw data never touches the chain. Private items stay private — even from us.
Mutable scopes
Stable tokens, server-side permissions. Revoke a partner's access without rotating every credential.