The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
AI agents need the ability to transact but they shouldn’t have unlimited access to a user’s wallet.
That’s why we built Seedhape.
Seedhape gives autonomous agents purchasing power within clear, user-defined boundaries.
A user can create a signed spending mandate that controls:
→ What the agent may purchase
→ The maximum amount per payment
→ The total daily allowance
→ The number of permitted transactions
→ Approved merchants
→ When the authorization expires
The agent receives a dedicated wallet and can operate through tools such as Claude, but every payment remains constrained by the signed mandate.
Before executing an x402 payment, Seedhape checks the merchant, price, network, allowance, and policy. Every completed transaction is recorded with its receipt and on-chain reference.
For merchants, the Seedhape SDK adds x402 payment gates to Express, Hono, and Node services with facilitator verification, direct USDC settlement, and transaction receipts.
Connected through AI. Authorized by your wallet. Bounded by your mandate.
Here’s the complete flow
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
I automated my entire customer onboarding process using one n8n workflow.
Dropping the ball on day one costs you lifetime customers.
You close a deal. The client is excited.
Then your team forgets to send the welcome package.
Or you pay a customer success manager $70k a year to manually trigger emails and update the CRM.
It is a slow, expensive bottleneck.
I stopped relying on human memory for week-one operations.
Here is exactly what this architecture executes:
→ Data Capture: A webhook catches the new signup and validates the client info.
→ Instant Action: It builds the HubSpot profile and alerts the team via Slack.
→ Time-Delay Sequences: Welcome email instantly. Docs at hour 2. Check-in at day 1. Success guide at day 3.
→ The Loop: It updates the CRM status the moment onboarding is complete.
Here is the ROI:
→ Zero manual admin work for your team
→ Flawless, professional first impressions
→ Week-one client churn dropped to absolute zero
If you want to work with me to build a similar automation in your business, I have a few spots open in my calendar this month.
Book a call here
AI Agent Developer work only counts when the workflow survives the handoff to a real team.
For Dispatchly, I built the product and stack behind an outbound voice calling workflow: teams can bring in leads from a CSV, a CRM, or by hand, then route qualified conversations into their CRM.
I build with approvals, read-back, and real integrations in the loop, so the system stays usable after the demo.
If your phone workflow is carrying too much manual work, message me with the call type.
Flowfolio
What it is
A Notion template for freelancers who bill through Stripe: two linked databases (Clients, Deals) with Kanban, Calendar, and List views, kept in sync automatically — when a client pays, the deal card moves itself to "Paid" instead of you dragging it by hand.
Components & how it works
The product itself lives in Notion — no separate app to log into. Deals has a Status select (Proposal → Sent → Paid / Failed / Refunded), a relation to Clients, and date/amount properties; the same data drives all three views (Board grouped by status, Calendar keyed on payment date, List sorted by value) for free, since they're just different lenses on one database.
The relay — a single Next.js API route (/api/stripe-webhook) deployed as a Vercel serverless function, on the buyer's own free Vercel account.
Event handling — Stripe's SDK (stripe.webhooks.constructEvent) verifies each request's signature before anything else runs (anything unsigned gets a 401); a small dispatcher routes four event types — checkout.session.completed, invoice.paid, invoice.payment_failed, charge.refunded — to their own handler.
Notion API (@notionhq/client) — each handler looks up the matching Deal page by its stored Stripe Invoice ID and updates its Status and Payment Date properties directly.
Idempotency — an in-memory set of processed Stripe event IDs prevents a re-delivered webhook (Stripe retries if it doesn't get a fast 200) from double-updating the same deal.
No database of its own — the relay is stateless glue between Stripe and Notion; it runs entirely inside the buyer's own Stripe, Notion, and Vercel accounts, so no third party (including the seller) ever touches their payment data.
