The developer track

Read a wallet. Check a condition.
Act on a signed answer.

That's wallet auth: the primitive under everything Skye Meta ships. A wallet is read, your conditions are evaluated, and you get back a cryptographically signed yes-or-no that anyone can verify. No accounts to manage, no secrets to store, no identity collected. Here it is as tools you build with.

See the three tools InsumerAPI docs Skye Meta on GitHub

The primitive

The category is condition-based access: instead of asking who someone is, you ask whether their wallet meets your conditions, and act on a signed answer. It's all powered by InsumerAPI, the condition-based access API.

Three tools, three questions

Pick the question your product is asking.

SkyeProfile

“Who is this wallet?”

The complete wallet trust profile. One call returns eleven independently signed dimensions across ten issuers (holdings, behavior, operator, control, code, sanctions, and more), each signature checkable offline. You rely on each issuer's method, not on us. Including us.

AgentTalk

“Can this agent be in the room?”

Condition-gated sessions for AI agents. Every participant's wallet is attested on entry and re-checked on demand; when on-chain state changes, the next check says so. Sell the token, lose the session. Crypto-paid credits, fully programmatic.

@skyemeta/access

“Can my API serve wallets too?”

Free, MIT either-or middleware for Node APIs. Your API-key customers pass through untouched; wallet-signed requests get verified. Bring your own InsumerAPI key, no Skye Meta license. If we disappeared tomorrow, it keeps working.

Which one do you need?

A finished product, or the building block?

Skye Meta builds products on InsumerAPI. If one of them answers your question, use it. If you're building something of your own, go one layer down.

Skye Meta

Finished products that each answer one question

Know a wallet with SkyeProfile, gate a room for agents with AgentTalk, open your API to wallets with @skyemeta/access, or show members-only content in your Next.js app with SkyeGate. Drop one in and you're done.

InsumerAPI

The condition-based access API underneath

Send any condition on any of 37 chains and get a signed yes or no. REST, an MCP server for AI agents, and pay-per-call with no key. For when you're building a product of your own.

InsumerAPI docs →

Why build on it

No secrets. No identity-first. No static credentials.

Nothing to leak

There's no API secret sitting in a config file waiting to be pasted into a gist. The wallet signs; the answer is signed back. Credentials that can't be copied can't be stolen.

Nothing to collect

You learn one thing: does this wallet meet the conditions? No emails, no PII, no customer database to maintain, breach, or subpoena.

Nothing goes stale

Conditions are evaluated against live on-chain state. When a wallet stops qualifying, the next check says no: no revocation workflow, no deny-list to scrub.

Verify it yourself

Every answer is signed and checkable against a public JWKS. You don't have to trust our uptime story or our word. Check the signature and move on.

Where these primitives run all day

One membership. Recognized everywhere.

The same read-evaluate-sign loop powers the Recognition Network: a community issues one pass through Bothy, and websites, stores, registers, and doors recognize it, live, thousands of times a day.

See the Recognition Network

Read a wallet. Check a condition.Act on a signed answer.