Manifest — Loyal Spark
The founder’s case for $LOYAL
Onchain loyalty on Base for merchants and AI agents.
Problem
Loyalty is still trapped in closed SaaS ledgers. Points are database rows, not owned value, and terms can change overnight. Small businesses pay for tools that lock customers inside someone else's app, and those tools rarely talk to wallets or agents. Customers can't move or trade balances outside one brand portal, so value dies in a silo.
AI agents already operate online, but they can't issue, earn, redeem, or exchange loyalty without a human dashboard.
Who it's for:
- Small businesses (cafes, retail, services, local chains) that want modern loyalty with points, rewards, and vouchers, without a closed points cabinet
- Their customers: people who earn and redeem value they actually own
- AI agents that can act as merchants or customers on the same rails (REST/MCP/x402)
We ship this on Base so loyalty can live onchain, but the pain we solve is everyday SMB loyalty, not crypto for crypto's sake.
Solution
Loyal Spark gives small businesses an onchain loyalty program they control: create a branded program, mint points for purchases, run rewards and vouchers, and bring customers back without locking them inside someone else's points app.
For merchants, the upside is practical:
- Customers return to you, not to a closed loyalty cabinet. Points live with the customer, but they spend them with you.
- Faster launch: deploy, mint, rewards, vouchers, without rebuilding token infrastructure.
- Less manual work: portal or API/agents can mint and check vouchers, so ops scale without a bigger staff.
- Clearer trust: onchain balances and redemptions reduce "where did my points go?" disputes.
- Room to grow: start at the counter, then add online flows and AI agents on the same rails.
Customers earn, hold, transfer, redeem, and can P2P-exchange loyalty value. Agents use the same loop via REST, MCP, and x402. Live at loyalspark.online.
Progress
- Built withCursor
- ModelClaude Sonnet 5
- GH@aspekt19
Live on Base mainnet:
- Product: https://loyalspark.online — merchant + customer portals (web/PWA; Capacitor ready for App Store / Google Play)
- Programs: B20 by default (one-tx deploy); mint, transfer, redeem, vouchers
- P2P: escrowed offers so loyalty value can move between programs
- Agents: REST + MCP for merchant (lsk_) and recipient (rwk_) roles; SIWE registration without mandatory web login
- Payments: x402 USDC pay-per-call. Live agent usage is visible on https://agentic.market/services/api-loyalspark-online (per-endpoint calls and payers) and listed on https://www.x402scan.com/server/b83f21f5-bdf9-4417-a2b3-0a0cb5e773c0
- Discovery: OpenAPI, agent.json, skills docs, /for-agents
Early signal: a live paid agent corridor and continuous mainnet activity. Monetization is live (merchant plans + agent pay-per-call + mint fee). We do not claim scaled merchant revenue yet. First paying design-partner merchants are the near-term goal.
Token
- Ticker$LOYAL
- Supply1,000,000,000
- ChainBase
- Founder7.5%
- Treasury10%
$LOYAL is the platform token. Merchants still issue their own B20 program tokens for customers.
Utility roadmap (after token launch; not live today):
Merchants:
- Hold: SaaS discounts + lower mint fees (on-chain)
- Stake: higher API limits for agents (REST/MCP/x402)
- Vote: treasury + roadmap via Snapshot
Customers / buyers (people who earn points):
- Hold: earn/redeem boost at participating programs
- Hold: lower P2P fees between loyalty programs
- Hold: early access to partner rewards and new merchants
- Stake: stronger boost tier
Marketplace: P2P stays in B20 program tokens; platform fees (and later routing) can be paid in $LOYAL.
Not a coffee payment method. Not a revenue share. Utility = merchant savings + customer boosts + agent capacity + governance + marketplace fees.
Use of Funds
- Release10% + 15% × 6
- ↓Funding schedule
~6 months shipping on the tranche schedule:
- Mobile apps (largest) — Customer + Business apps to App Store and Google Play; QA and web-loop parity.
- Minimal-blockchain UX + Paymaster — make chain barely felt in everyday use; implement and fund Paymaster on Base so users are not blocked by ETH gas.
- Merchant pilots and GTM — design partners, case studies, self-serve under 30 min; path to 3-5 paying merchants.
- Infra — production, billing, agent auth, P2P/escrow UX.
- Agent growth + AI payments — MCP/skills onboarding, external x402 usage, and AI payment costs.
Solo full-time founder. Spend: product development, App Store/Google Play release, infra, Paymaster, AI payments — not a large team payroll.
Platform analysis
The wedge is loyalty an agent can run end to end, from issuing a program token to redeeming a voucher, without a human ever opening a dashboard.
Two buyers sit behind this, and they are not equally reachable: the small merchant is the stated one, while the agent operator is the one the product is actually built to serve, and the trigger for that second buyer is needing a loyalty primitive callable at the moment of a transaction rather than at the end of a signup flow. Parity is the defensible part: every merchant and recipient action exists as a route and a tool, with keys issued without a web login, and that dual build is expensive enough that it is not casually copied. Deploying a branded token in one transaction is the copyable part. The public surface is unusually disciplined about proof, sending a reader to third party pages and onchain settlement rather than quoting its own numbers, which is a posture rather than a result but an uncommon one to choose. Pricing per call in stablecoin, at fractions of a cent, is the decision that reveals the most: it only makes sense if the API is the product and the web app is the wrapper.
// AI-generated by Claude from the live app and the founder's manifest · Aug 4, 2026 · Not an endorsement and not the opinion of Vibestarter. Not investment advice.