Skip to main content

You have a ~handle. Now what?

What ~alter does for you, and for the way you already work.

What does it actually know about me?

Your identity is inferred from what you do, never from what you claim. Attunement is how legible you have become: it rises as more of your real work is observed, and it is yours to read at any time.

$ alter status

~maya · Augmented (L3)

attunement 0.72 rising

sources github, obsidian, discord (3 paired)

discovery on · resolvable by field callers

earned $86.20 to date

Pick a question, and see what the CLI answers with.

Already included for free

All of it comes with the ~handle at no cost, and none of it is a tier you upgrade into.

Sessions that can see each other

Every session signed in under one ~handle sees what the others are already mid-flight on.

Context that survives the session

Hand your context over when you stop, and the next session picks it up with nothing to paste.

Commits that name who wrote them

Authorship binds to the ~handle in your live session, not to a value sitting in a config file.

A vouch the subject agreed to

One ~handle attests a named competence about another, and it lands only if the subject granted it.

A part that stays awake

An optional background program holds what your ~handle knows on this machine, signature-checked before it runs.

Sources that speak for you

You pair sources one at a time, nothing is ever read from something you did not pair, and most of them prove themselves with a signed challenge or a string you publish rather than a login.

Skills for the clients you use

The CLI installs skills into the AI clients on your machine, and each one is published under the ~handle that wrote it.

Found without being told

~alter is listed in the official MCP registry and 7 other directories, so a client or an agent that goes looking already finds it.

A folder checked for quiet rot

Point alter doctor loom at a folder of student records or eldercare paperwork: it flags corrupted text, broken links, an exposed password. Nothing leaves the machine.

Knowing which agent is free

A consent-gated presence grant resolves through the roster, so another ~handle can see you are reachable.

Choosing a skill without guessing

Whoever published a skill is a ~handle you can look up, free, before you install anything.

Which session spent that

The namespace names instruments apart from people, so a session is nameable in its own right.

Three commands, one decision

Install the CLI, then make the only decision there is, whether you are minting a new ~handle or signing in to one you already hold. The third command writes the config for the AI clients on this machine, which is the list under it.

# matched to your platform, the other platforms each get their own line
curl -sSf https://truealter.com/install.sh | bash
alter register   # or alter login
alter wire
  • Claude Code
  • Cursor
  • Claude Desktop
  • VS Code

Anything else takes a URL, because ~alter is a hosted MCP server any client can point at.

https://mcp.truealter.com/api/v1/mcp

Give your agent its own ~handle

Everything above assumes a person at the keyboard. Software that acts on its own can hold a ~handle in its own right, with no human account behind it, so it is identifiable to whatever it talks to and coordinates with other ~handles as itself rather than as whoever ran it.

Start at the manifest. It names the endpoint, what costs nothing, and the two calls that mint the ~handle. After that it is the same MCP surface the clients above connect to, so there is no second stack to build against.

GET https://truealter.com/.well-known/mcp.json

call register_autonomous_challenge, then register_autonomous · auth: none · price: 0

Reference

registries8
source3
docs7
  • Getting started

    First call in under five minutes. API key, MCP handshake, verify_identity.

  • Protocol stack

    How every part of ~alter behaves, so you can build against it and integrate it into your own stack.

  • MCP tool reference

    Read tools are open to call. What they return is bounded by what the subject consented to share. Messaging tools need a per-peer grant on top of that.

  • OAuth scopes

    identity_read and identity_write carry the same consent boundary as the MCP read tools. Scoped to what the subject granted, revocable any time.

  • x402 micropayments

    Free tools and paid tools, $0.01 to $1.00 per call. USDC on Base. 75% of every paid call routes to the data subject.

  • ~handle protocol

    Three-tier namespace: Sovereign, Bot, Instrument. Resolution via DNS-TXT discovery.

  • Connectors

    Every source pairable to a ~handle, grouped by how each proves control. Most need no application registered and no credential held: a signed challenge, or a string you publish yourself.

standards18

contact

TermsPrivacySecurityDocs