endpointme.world

What is endpointme.world?

endpointme.world is a service for publishing a person as a machine-readable API endpoint. It turns identity details, skills, status, and proof of work into signed JSON that can be fetched by browsers, apps, and agents.

The product centers on a public profile endpoint and a verification layer. Profiles are anchored to a did:key identity, signed with Ed25519 in the browser, and exposed with metadata such as freshness, confidence, and proof sources so automated systems can decide whether to trust the data.

Key Features

• Public profile endpoints: users can publish a clean JSON profile at a handle-based URL such as /yourname, making identity and skills easy to fetch programmatically.
• DID-anchored identity: each profile is tied to a did:key, giving the profile a cryptographic identity without blockchain, wallets, or gas fees.
• Browser-side signing: profile updates are signed with Ed25519 in the browser, and the private key stays local to the user’s device.
• Verification endpoints: agents can call /verify, /[username]/verify, or batch verification endpoints to check signatures and receive a trust verdict.
• Trust metadata: responses include fields such as signed_at, freshness, confidence, and proof sources so consumers can assess whether the profile is current and well supported.
• Live status fields: profiles can include availability and other live status information, making them suitable for current outreach or matching workflows.

How to Use endpointme.world

Start by claiming a username and generating a DID in the browser. Then fill in profile fields such as skills, projects, availability, and other details you want machines to read.

When you save changes, the profile is signed automatically and published as JSON. You can share the endpoint directly, and agents or apps can fetch the profile and verify the signature before using the data.

Use Cases

• Agent research on people: an AI agent can fetch a structured profile instead of scraping a portfolio page or parsing messy HTML.
• Collaboration discovery: people can signal that they are open to freelance work, collabs, or other opportunities in a format that is easy to query.
• Recruiting and sourcing: teams can search for candidates by skills and availability, then review proof signals before reaching out.
• Network introductions: tools can compare two endpoints to draft an intro based on overlapping skills, complementary experience, or shared interests.
• Live availability sharing: users can embed a current status endpoint in a bio, README, or signature instead of relying on a static “open to work” line.

FAQ

• Is the profile data signed? Yes. The product signs profile updates with Ed25519 and includes signature and trust metadata in the response.
• Does it use a blockchain or wallet? No. The source explicitly says it uses did:key and Ed25519 signing without blockchain, gas, or wallet requirements.
• What does verification return? Verification endpoints return a verdict such as high_trust, low_trust, or invalid, along with freshness, confidence, and proof-source details.
• Can agents verify data locally? The source says agents can verify signatures with pure math, so local verification is part of the intended workflow.
• What kind of information can be published? The examples show usernames, headlines, skills, availability, projects, and proof-related metadata, but the exact schema may vary by profile.

Alternatives

• Traditional personal websites: these are better for narrative portfolios and visual presentation, but they are not designed as signed, machine-readable APIs.
• Social profiles such as LinkedIn: these are useful for discovery and networking, but they are not presented here as verifiable JSON endpoints for agents.
• Static JSON resumes or profile APIs: these can expose structured data, but they may not include the same built-in DID anchoring, browser-side signing, and verification flow.
• Talent search or recruiting databases: these support sourcing and filtering, but they usually serve a broader marketplace workflow rather than a personal endpoint owned by the individual.