Pascal Glass
See who traded. Prove what your agent did.
Read every named Pascal fill with no API key, and check each agent order against its written intent.
Try it: no key
The request below is the one this page just made.
curl -s "https://pascal-glass.pages.dev/v1/wallets?window=1d&sort_by=taker_notional&limit=2"
loading…
Why it exists
Agent builders ask for your trading key and your trust. Pascal already shows both wallets on every public fill, and a trading key cannot withdraw. Nobody uses that yet: 0 of 7,206 fills carry a builder code. Glass turns the open record into an API and checks each agent order against it.
Sources: "0 of 7,206": branch-B2B V2. "cannot withdraw": PRIMITIVES §1.
| Surface | What it does |
|---|---|
| The Board | Ranked wallets by realised PnL, with house-desk and bot tags and the sample size beside every figure. |
| The Other Side | Pick any fill and see who took the other side. |
| Glass Replay | Replay what a copy of this wallet would have earned: 60 seconds late, $10 a fill. |
| The Verifier console | One receipt per order: intent, rules, verdict, signature, devnet record, matching fill. |
Endpoints
Status from openapi.yaml x-status. A stub returns 501 with implement_at.
| Method | Path | Status | Parameters | Returns |
|---|---|---|---|---|
| GET | /v1/health | live | — | Service health and data window |
| GET | /v1/wallets | live | window, sort_by, label, min_fills, limit, cursor | Leaderboard of wallets |
| GET | /v1/fills/{trade_id}/counterparty | live | trade_id | The other side of one fill |
| GET | /v1/wallets/{owner} | stub · 501 | owner | One wallet profile |
| GET | /v1/wallets/{owner}/positions | stub · 501 | owner, held_until_resolution, limit, cursor | Position instances for one wallet |
| GET | /v1/fills | stub · 501 | symbol, wallet, since_seq, limit | Named fills, deduplicated on trade_id |
| GET | /v1/markets/{symbol}/flow | stub · 501 | symbol, window | Taker flow and who is on each side of one market |
| GET | /v1/labels | stub · 501 | label, rule_version | Wallet labels with rule version and evidence |
| GET | /v1/replay/{owner} | stub · 501 | owner, stake, lag_s, fee, cols | Glass Replay, copy one wallet with a lag |
| GET | /v1/attestations | stub · 501 | kind, signer, since | Hash-log records (ATTEST and RESOLVE) |
| GET | /v1/attestations/{sha256} | stub · 501 | sha256 | One attestation by record hash |
| POST | /v1/verify | stub · 501 | demo key; intent, order | Check an agent order against its intent, sign and log the verdict |
Privacy. No handle shown until Pascal approves. We show only whether an X account is linked.
Every keyless route, its parameters and a sample response.
It does not promise uptime or rate numbers for paid tiers yet.
Pricing
Prices: DATA-LAYER §3.
Keyless reads of named fills, wallets, labels and replays, at a rate limit.
One key, higher rate limit.
Redistribution licence, pending Pascal approval.
$0 cash, co-marketing, campaign audit.
The three asks to Pascal
- RedistributionPlease confirm in writing that we may redistribute public fill and wallet data through the Glass API.
- Data partnerWe ask to be listed as a Pascal data partner, with agreed rate limits and a named contact.
- Signed feed and pilotWe ask for a Pascal-signed resolution feed and a builder-code pilot with a 50 % leader share.