SolMachina vs a raw data feed
A raw data feed hands your agent numbers and hopes it decides well. SolMachina returns the decision — EXECUTE / REVIEW / REJECT — enforces your policy, and ships a signed receipt that proves the answer. Point both at the same tokens for a week. Let the facts decide.
Every row is checkable against our live endpoints right now — no marketing, no asterisks.
| What your agent needs before it moves money | Raw data feed | SolMachina |
|---|---|---|
| Answer | raw fields, you interpret | a decision + risk index + evidence |
| Your risk policy, enforced | — | ✓ fail-closed ALLOW/DENY firewall |
| "Can I actually sell it?" (honeypot/exit) | rarely | ✓ live exit-liquidity round-trip |
| Backdoor surface composed (permanent-delegate / transfer-hook / sell-tax) | raw flags at best | ✓ scored into one verdict |
| Proof the answer is real | trust me | ✓ Ed25519 receipt, verify offline |
| Machine-executable authorization (with expiry) | — | ✓ Proof-of-Decision envelope |
| Says "unknown" instead of guessing | often a black box | ✓ honesty contract |
| Pay | account + API key + invoice | no account, pay-per-call USDC (x402) |
| Rails | usually one | Solana + Base |
Wire SolMachina in parallel with whatever you use today — don't switch anything. For a week, on the same tokens, measure:
coverage · which one flags the rug the other missed? unknown-rate · who admits "unknown" vs guesses? unique fields · exit-liquidity, permanent-delegate, signed authorization verifiable receipts· can you cryptographically prove the answer after the fact? cost · $0.001–$0.10 per call, no account, no minimum
Then keep whichever earns its place. We only win if the facts say so — and they're all verifiable: signed receipts, npx solmachina-verify, live status.
npm i solmachina-sdk # the firewall in three lines # or connect the remote MCP: https://api.solmachina.com/mcp