PAYNAPTIC

Building the thing people won't realize they needed until the first agent wallet gets drained. We'd rather be early than right on time.

Agents don't sleep. Neither does the policy engine. Every transaction. Every hour. Every day. Checked on-chain before it clears. Paynaptic.

On a public L2, your agent's entire playbook is readable from a block explorer. How much it can spend. What tokens it uses. Which suppliers it works with. When it operates. For any serious operation, that's a dealbreaker. zkPolicy is live. Policies are now enforced under zero-knowledge proofs. The rules hold. The chain validates. But the details are gone. Commitments and nullifiers only. No amounts. No counterparties. No limits exposed. Private tab is live on the dashboard.

Two upgrades to Policy Copilot. Named recipients, label the addresses your agent pays so Copilot resolves them deterministically instead of guessing. Golden eval harness, a pinned NL→policy test set, so a model or prompt change can never silently drift what your English compiles to. Same guarantee, more hardened.

Just shipped Receipt Rails on @Paynaptic Point any HTTP API at us → it becomes pay-per-call. • unpaid request → x402 402 challenge • paid request → verified, proxied, returned with a signed receipt The toll road for the machine economy. Built on @base

Things Paynaptic agents can do at 3am while you sleep: • Pay for compute • Settle API calls • Rebalance positions • Buy sensor data • Pay road tolls Things they can't do: • Spend more than you allowed • Touch tokens you didn't whitelist • Interact with unapproved contracts • Operate past key expiry That's the product.

The first agent that gets drained on live mainnet will be a bigger headline than any hack this year. And it'll happen to a project that thought a backend rate limit was enough. We built different.

New drop. Sentinel is live. What it does: scores every agent's spending behavior against its own 14-day baseline. Flags anomalies — velocity spikes, new recipients, denial bursts, rapid-fire patterns. What happens next: circuit breaker trips automatically. Two modes: • FREEZE, scope locked in seconds • KILL, session key revoked entirely Frozen agents also lose gas sponsorship through the Synaptic Paymaster. No gas = no transactions = no damage. Self-defending money for the machine economy. Sentinel tab is live.

In 5 years every AI agent will have a wallet. The question isn't whether that happens. It's whether those wallets have rules. Spending limits that can't be overridden. Session keys that expire. Policies enforced by the chain, not a server. Transactions shielded from competitors. That's the bet. That's Paynaptic.

New on Paynaptic: the Agent Reputation Graph. Per-agent spending limits can't see a sybil swarm draining you $2 at a time, or money looping A→B→C→A to launder it. So we built a fleet-wide money-flow graph that does, scoring every counterparty for risk in real time. Catch what single-agent rules miss.