Home/Digital Identity APIs/EndpointMe
E
EndpointMe logo

EndpointMe

Updated: Nov 18, 2026

Claim a signed, machine-readable human profile so developers and AI agents can query your skills, availability, and proof of work โ€” then verify the payload before they trust it.

Image not available

About EndpointMe

Overview

EndpointMe turns a person's identity, skills, availability, and proof of work into a signed, machine-readable endpoint at endpointme.world/yourname. People, apps, and AI agents query that endpoint as clean JSON instead of parsing a messy portfolio site.

Every profile ties to a did:key identity derived from an Ed25519 public key that your browser generates. The private key stays in local storage and only the public key reaches the servers, so each profile save produces a signature an agent can check before trusting the payload. Verify endpoints return a verdict of high_trust, low_trust, or invalid alongside freshness, confidence, and proof sources such as GitHub and collaborator attestations.

Key Benefits

  • Your handle returns structured JSON covering headline, skills, availability, and proof sources rather than a scraped web page.
  • A did:key identity anchors each profile without a blockchain, gas fee, or wallet.
  • Your browser signs every profile change with Ed25519, and the private key never leaves the device.
  • Verify endpoints answer with a high_trust, low_trust, or invalid verdict on demand.
  • A 0โ€“1 confidence score rolls freshness and proof signals into a single number agents can compare.
  • Human search filters people by skills, collaboration intent, and location.

How It Works

Claim a username, which takes roughly 30 seconds and locks in endpointme.world/yourname. Your browser then generates an Ed25519 keypair and a did:key identity, keeping the private key local. You fill in skills, projects, availability, and the signals you want machines to read, and every save signs itself automatically. You share one link in bios, intros, and outreach, and agents call GET /you/verify to check the signature with pure math and read the verdict.

Use Cases

  • AI research agents call GET /username to pull clean structured data for candidate research and personalized outreach.
  • Builders and freelancers query /search/humans by skills, open_to, and location to find people who are actively open to collaboration.
  • Recruiters and startups search on exact skills plus availability and see matching projects that back up the claims.
  • Networking tools and bots read two endpoints, spot overlapping skills, and draft a personalized introduction.
  • Developers embed /:username/status in an email signature, Notion page, or GitHub README to keep availability current.
  • Agent pipelines call POST /verify/batch to sort profiles into trusted and untrusted before acting on them.

Why Choose This Product

EndpointMe skips blockchain tooling: identity is did:key, signing happens in the browser, and verification runs on Ed25519 math, so agents check profiles locally without a trust-us API call. Search and batch verification ship in V1. The tradeoff the site names directly: losing the browser key means re-registering, because the private key never leaves your device.

EndpointMe Pros & Cons

Strengths
  • did:key identity with Ed25519 signing, no blockchain, wallet, or gas
  • Private key stays in browser localStorage and never reaches the servers
  • Agents can verify signatures locally without calling a trust API
  • Verify endpoints return high_trust, low_trust, or invalid verdicts
  • Human search filters by skills, open_to intent, and location
Limitations
  • Losing the browser key forces re-registration (stated V1 tradeoff)
  • Private key lives in browser localStorage, so it is tied to one device

Key Features

๐Ÿง‘โ€๐Ÿ’ป

Human Endpoint

Each username publishes a profile as clean JSON that people, apps, and AI agents can read.

๐Ÿ”‘

DID-Anchored Identity

Every profile ties to a did:key cryptographic identity generated in the browser from an Ed25519 public key.

โœ๏ธ

Signed Updates

Each profile save is signed automatically in the browser with Ed25519, and the private key stays on your device.

โœ…

Trust Verification

Agents use GET /:username/verify, GET /verify?did=..., or POST /verify/batch to obtain a high_trust, low_trust, or invalid verdict.

๐Ÿ“Š

Confidence Scores

Freshness and proof signals combine into a 0โ€“1 score so agents know how much to trust the payload.

๐ŸŸข

Live Availability

Profiles show what you are open to, what you are busy with, and how quickly you reply.

๐Ÿ”Ž

Human Search

GET /search/humans filters people by skills, open_to intent, and location.

๐Ÿชช

Status Badge

Embed /:username/status in an email signature, Notion page, or GitHub README to show real-time availability.

๐Ÿ”

Visibility Control

Profiles rely on explicit, public fields, and only visible data enters the signed payload.

โ›“๏ธ

No Blockchain Needed

The did:key method delivers verifiable identity with no gas fees, no wallet, and no chain.

Frequently asked questions about EndpointMe

Is EndpointMe a portfolio?

It can serve as one, but the core product is the API-shaped version of you: a signed, verifiable, agent-ready profile published at endpointme.world/yourname and readable as clean JSON.

What is a DID on EndpointMe?

A Decentralized Identifier. EndpointMe uses did:key, a blockchain-free identity derived from your Ed25519 public key, with no gas fees, no wallet, and no chain.

Where is my private key stored?

In your browser's localStorage. It never leaves your device, and the servers store only your DID and public key. If you lose the browser key, you need to re-register โ€” the tradeoff the site names for V1.

How do agents verify a profile?

Three ways: GET /:username/verify for a verdict, GET /verify?did=... to resolve by DID, or POST /verify/batch for pipelines. Agents can also verify the Ed25519 signature locally with pure math, without any API call.

Who is EndpointMe built for?

Builders, freelancers, candidates, recruiters, teams, and agents that need structured human context they can trust.

Can I control what is visible on my profile?

Yes. The profile is designed around explicit, public fields instead of scraped guesses, and only visible data is included in the signed payload.