# Dimes

> Dimes is embedded credit infrastructure for onchain platforms. Its flagship product, Multiply, is a middleware protocol that lets prediction market front-ends (trading terminals, wallets, apps) natively offer users up to 10x leveraged exposure on Polymarket positions — without building internal leverage infrastructure. Dimes handles all credit provisioning, hedging, risk management, and settlement. Backed by Coinbase Ventures, Accel, and others.

Dimes operates a B2B model: it does not compete with prediction market venues or acquire users directly. Instead, front-end applications integrate Multiply via a REST API to unlock leverage as a built-in feature. An institutionally-sourced Underwriting Facility with $100M+/month capacity guarantees credit availability regardless of market conditions — no reliance on pool-based TVL.

Core products:
- **Multiply**: Up to 10x margin-funded directional leverage on prediction market positions via Contract-for-Difference (CFD) structure. Supports binary and simple categorical markets on Polymarket. Planned expansion to Kalshi, Opinion, Hyperliquid, and Limitless.
- **Firepower**: Native portfolio margining across top 50 liquid tokens, freeing capital without introducing leverage.
- **Stream**: Continuous synthetic exposure to assets like BTC/ETH, sized automatically against existing holdings.

Revenue model: platforms earn 30% of fees generated by their users across all Dimes products — entry fees, time-based funding fees, and liquidation fees. Zero operational overhead for partners.

Technical: Polygon mainnet, USDC settlement, 2x-10x leverage in 0.25x increments, sandbox mode for development, WebSocket real-time updates, two-tier authentication (API keys + JWTs).

## Documentation

- [What is Multiply](https://docs.dimes.fi/overview/readme): Core product overview — middleware leverage layer for prediction market front-ends
- [Supported Markets](https://docs.dimes.fi/overview/supported-markets): Market eligibility criteria based on event type, liquidity microstructure, and safe margining
- [Position Lifecycle](https://docs.dimes.fi/positions/position-lifecycle): How leveraged positions are opened, monitored, hedged, and settled
- [Fees & Revenue Share](https://docs.dimes.fi/positions/fees-and-revenue-share): Fee structure (entry, time-based, liquidation) and 30/70 partner revenue split
- [Integration with Front-Ends](https://docs.dimes.fi/positions/integration-with-front-ends): Drop-in margin infrastructure for prediction market terminals
- [Synthetic Exposure](https://docs.dimes.fi/leverage-and-risk/synthetic-exposure): How collateral and hedging create synthetic leveraged positions
- [Contract-for-Difference](https://docs.dimes.fi/leverage-and-risk/contract-for-difference): Why CFDs over perpetuals, collateral loops, or options for prediction market leverage
- [Leverage Decay (J-Factor)](https://docs.dimes.fi/leverage-and-risk/leverage-decay-j-factor): Automated microstructure-driven exposure reduction protecting users and facility
- [Margin Requirement](https://docs.dimes.fi/leverage-and-risk/margin-requirement): Position sizing, collateral rules, and liquidation thresholds

## Developer Resources

- [Quickstart](https://docs.dimes.fi/for-developers/quickstart): Get a working integration operational in hours — authentication through position closure
- [Sandbox Mode](https://docs.dimes.fi/for-developers/sandbox): Test all API endpoints with realistic data, no contract deployment or funds required
- [On-Chain Integration](https://docs.dimes.fi/for-developers/on-chain-integration): Transaction submission and automatic backend handling for position operations
- [Authentication](https://docs.dimes.fi/for-developers/authentication): Two-tier model — partner API keys and short-lived wallet-scoped JWTs
- [API Reference](https://docs.dimes.fi/for-developers/api-reference): Complete endpoint documentation (markets, quotes, positions, user-limits)
- [WebSocket Events](https://docs.dimes.fi/for-developers/webhooks): Real-time position updates via Socket.IO connections
- [Error Handling](https://docs.dimes.fi/for-developers/error-handling): Consistent error response format with type, code, and human-readable messaging
- [UI Guidelines](https://docs.dimes.fi/for-developers/ui-guidelines): Reference implementations with visual examples and API field mappings

## Optional

- [Dimes Homepage](https://dimes.fi): Main website with product overview, investor logos, and integration CTA
- [Partner Portal](https://partner.dimes.fi): Revenue tracking and performance data for integrated platforms