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
The primitive Wallet auth: read, evaluate, sign A request arrives with a wallet. InsumerAPI reads what the wallet holds, evaluates your conditions, and returns a signed boolean answer your code acts on. ONE CALL · ONE SIGNED ANSWER A wallet arrives at your door READ what it holds 37 chains EVALUATE your conditions tokens · NFTs · more SIGN yes or no, verifiable by anyone Your code The answer is a signed boolean — never balances, never identity. Check the signature yourself: trust the math, not a company.

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

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 verifiable offline, without trusting anyone. Including us.

 AgentTalk

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 live; the moment on-chain state changes, access changes with it. Sell the token, lose the session. Crypto-paid credits, fully programmatic.

 @skyemeta/access

@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. BYO InsumerAPI key, no SkyeMeta license — if we disappeared tomorrow, it keeps working.
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

Start with the question you're asking.

Know a wallet, gate a session, or open your API — all on the same signed answer.

SkyeProfile AgentTalk @skyemeta/access InsumerAPI Docs