Use the Paragon app
Ask Lens and Volt before a swap, approval, DCA plan, or token decision. Good for users and beta testers.
Start with the product surfaceBuilder surface
Build agents that can act only after proof clears.
Paragon Agents are the first interface, not the whole company. Synapsek is building the full Paragon product family: Core, Agents, DEX surfaces, Task API, templates, adapter rails, and future protocol infrastructure.
Paragon StackCore + Agents + DEX
AppAPIProjectAgents
No custody. No agent signing. Adapter-ready.
01 Builder paths
Four ways to enter the Paragon stack.
Start narrow. Use one task, one template, one project agent, or one adapter. The same evidence and Guardian contracts can later expand into DEX, marketplace, protocol, and chain surfaces.
Call the Task API
Integrate market scans, token scans, route checks, wallet readiness, Guardian scores, DCA, and alerts.
Server-side integrationAdd a project agent
Give communities a Guardian agent for token reality, launch-flow checks, route readiness, and alerts.
Project-facing agentConnect an external rail
Use Agentverse, BNBAgent testnet compatibility, Trust Wallet handoff, or future adapters around Core.
Adapter path02 Agent templates
Templates should sell proof work, not promises.
The marketplace direction is policy-bound templates: reusable agents with allowed chains, allowed tokens, blocked actions, required proof, risk mode, and service fees.
Safe Meme Scanner
Meme and microcap watchlist with CEX/single-venue labels, liquidity proof, and avoid/watch/tradable gates.
template-ready directionConservative DCA Agent
Staged entries with market regime, route proof, wallet readiness, and no automatic execution.
template-ready directionLaunch Guardian
Project launch monitor for LP status, deployer posture, fresh-wallet behavior, and community warnings.
template-ready directionWallet Risk Monitor
Allowance, spender, wrong-chain, gas, concentration, and blocked-token memory for active wallets.
template-ready directionRoute Readiness Agent
Preview-only path checks for DEXs, wallets, and projects that need proof before handoff.
template-ready directionCommunity Alert Agent
Watchlist, liquidity, Guardian warning, and Volt-ready alerts for Telegram or app channels.
template-ready direction03 External agent rails
Adapters are distribution. Paragon Core stays the brain.
Agentverse, BNBAgent testnet, Trust Wallet, OpenClaw, Hermes, Telegram, and future frameworks should call Paragon Core instead of replacing it. The same applies across Paragon Agents, DEX handoff surfaces, templates, and future protocol rails. The adapter receives a bounded task response with evidence, missing proof, Guardian action, and handoff scope.
Agentversepublic profile, manifest, safe task adapter, agent1 pending
BNBAgenttestnet-only compatibility until official production support exists
Trust Wallettoolkit and user-signed handoff, not a hosted Paragon agent
Hermes/OpenClawinternal engineering or external adapter paths, not the Core brain
04 Integration checklist
What to build first.
- Decide the task surface: user app, server API, project agent, or external adapter.
- Keep Paragon Core as the evidence and Guardian layer, not a hidden execution engine.
- Use preview_only unless Guardian allows wallet_review and the user wallet signs.
- Expose missing proof instead of smoothing it away in UI copy.
- Treat templates as policy-bound services, not autonomous traders.
05 Current recommendation
Ship a proof surface before a marketplace.
The best next builder work is still provider depth, evidence-first specialist execution, route regressions, and final-copy validation. Once the trust layer is harder to copy, Paragon Agents, DEX surfaces, templates, paid tasks, dashboards, marketplace rails, and future chain infrastructure become much more valuable.
Integrate Task API