Brickken
Institutional RWA tokenization platform (ISO 27001/27701/27018, MiCA-aligned) with a no-code issuer studio and an API integration tier.
- Sato Score28
- ChainsBase, Ethereum +2
Brickken is a closed-source defi tool on Base, Ethereum, Polygon and other chains, with no code activity tracked. Sato Score 28/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
See how to install Brickken →No code activity tracked
Listed from brickken.com on 2026-07-19. Install: not attempted. Evidence →
Next step
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpAsk Sato Hub what is on record about Brickken before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Brickken is a compliance-oriented platform for issuing and managing tokenized real-world assets — equity, funds, real estate, commodities — on Ethereum, BNB Chain, Base, and Polygon, with built-in KYC/KYB and cap-table management. It offers three access tiers (Issuer Studio, White-Label, and API Integration), the latter letting a technical team wire specific issuance or compliance functions into an agent-driven workflow.
Sato Score
28/100· LowHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 0/20
- Interface verifiability
- 0/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 5/15
- Independent verification
- 3/10
Sato Check
v0.4.13 · as of 2026-09-29- Does it take your key?
- Reads a key
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from brickken.com on 2026-07-19. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Base, Ethereum, Polygon, BNB Chain | self-reported | brickken.com | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | brickken.com | as of 2026-10-21 |
| Install works | documented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_spec | self-reported | raw.githubusercontent.com | as of 2026-09-14 |
| Website answers | answered, but declined our check (HTTP 403) | observed | brickken.com | 2026-10-21 |
| Daily check record | 50 of 50 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| ERC-8004 registration | declared address not found in the registry | observed | — | 2026-10-21 |
| Takes your key | reads private-key material | traced | satohub.ai | 2026-09-29 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-29 |
| Sato Score | 28/100 (Low)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-21 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — not run by us — no falsifiable install+entry probe from deploy_spec
Runtime: Node.js (npm CLI package brickken-cli)
npm install -g brickken-cli brickken --version brickken <command> (x402-only auth; high-level commands are prepare-only by default, add --execute to sign and send)
You supply: BRICKKEN_PRIVATE_KEY (0x... — signs transactions and x402 payments locally; private key custody risk, do not hardcode), BRICKKEN_RPC_URL (blockchain RPC endpoint), BASE_URL (API endpoint, e.g. https://api.sandbox.brickken.com), CHAIN (chain id, e.g. 11155111 for Sepolia), WALLET (signer address)
Read from the project’s own docs as of 2026-09-14. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 51
- Failed
- 40
- Their error
- 0
- Unattributed
- 40
State changed on 2026-09-01 (unclear → responding).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.
Last 30 days — to 2026-10-21, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Base, Ethereum, Polygon, BNB Chain
- Agent types
- RWA tokenization platform
- Open source
- No
- Last checked
- 2026-10-21
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Brickken fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to Brickken's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 26, 2026Edited: entity class, resource type
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 21, 2026Edited: onchain address
- Jul 20, 2026Edited: deploy spec
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Definitive
ActiveA non-custodial trading platform and API offering algorithmic order types (TWAP, limit, stop) with smart order routing across many chains.
ChainAware
ActivePre-built MCP blockchain capability modules giving agents fraud detection, AML scoring, wallet profiling, and token analysis.
Carbon DeFi
ActiveAn on-chain trading protocol for automated, adjustable limit, range, and recurring orders that execute fully on-chain and non-custodially.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Brickken
- Is Brickken open source?
- No. Brickken is closed source as of 2026-10-21.
- Which chains does Brickken support?
- Brickken lists support for Base, Ethereum, Polygon, BNB Chain as of 2026-10-21.
- Is Brickken still maintained?
- Sato Hub tracks no commit or release for Brickken; it cannot say whether it is maintained.
- How do I install or run Brickken?
- Node.js (npm CLI package brickken-cli). Install: npm install -g brickken-cli && brickken --version. Entry: brickken <command> (x402-only auth; high-level commands are prepare-only by default, add --execute to sign and send). This is taken from the project's own documentation and has not been reproduced by Sato Hub.
- Is Brickken verified on Sato Hub?
- No independent verification is on record for Brickken; its verification status is "Unverified" and its Sato Score is 28 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Brickken — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/brickkenData last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.