attestedmemory / developers
Setup wizard
DEVELOPER PORTAL · PRODUCTION CONTRACTS

Ship your first proven memory.

Start with a free actor-bound key, make a signed request, then publish your own capability into the federated catalog.

—network capabilities
—indexed Hubs
10guide languages
attested://first-write
$ POST /memory/api/memories
X-SaaS-Keyask_••••••••scope ✓
X-Actor-Signatureed25519:••••identity ✓
201 CREATEDmem_9f2a…provenance: signed
MCP · STREAMABLE HTTP

One endpoint for agent access.

Paste the URL into an MCP client. Discover with market_search, invoke with market_invoke, then verify the hybrid-signed receipt.

market_searchmarket_invokeEd25519 + ML-DSA-65
PRODUCTION · MCP 1.0.1
https://hub.attestedmemory.net/mcp
Open live endpoint ↗
FIRST TEN MINUTES

One clear path into the network.

No blockchain transaction is needed for the trial. Your private actor key stays in your runtime.

01CHOOSE

Pick the product surface

Personal, Team or Expert Market. Every access key is product-scoped.

Open setup wizard →
02IDENTITY

Create an Ed25519 actor

Derive the did:actor identifier and sign that exact identifier locally.

See the request →
03INVOKE

Write or discover

Call the product API; Gateway checks scope and Hub preserves trust state.

Browse contracts →
04VERIFY

Keep the receipt

Persist the memory ID, truth state and provenance receipt beside the output.

Open Attested Prove →
TRIAL · STUDIO · RECEIPT

First signed write

Claim a Personal trial in the browser, then POST a Memory Unit. The studio shows the receipt, hash and cite pack.

COPY · SIGN · SEND

A complete first write.

The shell example assumes you exported an issued ask_ key and an actor identity. The Python example creates the actor locally before sending the same request.

The private key never becomes a header.Only the public key and signature leave your process.
curl -fsS -X POST https://attestedmemory.net/memory/api/memories \
  -H "X-SaaS-Key: $ASK_KEY" \
  -H "X-Actor-ID: $ACTOR_ID" \
  -H "X-Actor-Public-Key: $ACTOR_PUBLIC_KEY" \
  -H "X-Actor-Signature: $ACTOR_SIGNATURE" \
  -H 'content-type: application/json' \
  -d '{"title":"First signed memory","content":"A decision worth keeping.","tags":["quickstart"],"visibility":"private","source_refs":[]}'
CONTRACT ATLAS

Every public surface, one click away.

Use OpenAPI for direct product integration and the signed AI Market manifest for federated invocation.

CAPABILITY DISTRIBUTION

Yes — the Hub promotes its capabilities.

Promotion is automatic after authorization; trust is never self-approved.

01

Provider registers

A signed provider publishes its schema, price, invoke URL and public key.

02

Hub indexes

The catalog exposes discovery metadata and records capability consumption.

03

Hub announces

Federation bootstrap announces the signed Hub identity to configured roots.

04

Peers approve

External operators inspect and pin the identity before granting trust.

AUTOMATICRegistration, signed discovery, metrics and federation announcements.
OPERATOR CONTROLLEDPublisher token issuance, external approval and promotional channels.
MANIFEST LAB

Shape a capability before you publish it.

This local builder generates a starter AI Market v2 entry. It sends nothing and stores nothing.

Add the provider public key and obtain a scoped publisher token before registration.

curl -fsS -X POST https://hub.attestedmemory.net/ai-market/v2/supply/register \
  -H "Authorization: Bearer $AIMARKET_PUBLISHER_TOKEN" \
  -H 'content-type: application/json' \
  --data @capability.json

BUILD WITH EVIDENCE

From first request to federated distribution.

Use the trial for integration, OpenAPI for contracts and the signed manifest when your capability is ready for agents.