# Riftl.ink (Rift)

> Deep linking and attribution API. Built for humans, ready for agents. One link, two audiences: humans click and get redirected, agents resolve the same URL into structured JSON.

## Product

Riftl.ink is API-first link infrastructure for iOS, Android, and web. Rift handles short links, deep links, deferred deep linking, install attribution, and conversion tracking. Developer resources for Rift are published on `riftl.ink` and `api.riftl.ink`.

Pricing is usage-based with a free tier and paid plans for higher traffic and longer retention. Sign up, get an `rl_live_` API key, and POST to `/v1/links`.

## Developer Resources

- [OpenAPI JSON](https://riftl.ink/openapi.json): machine-readable API schema for Rift
- [Well-Known OpenAPI](https://riftl.ink/.well-known/openapi.json): predictable OpenAPI URL for agents
- [API Catalog](https://riftl.ink/.well-known/api-catalog): RFC 9727 linkset catalog for Rift APIs
- [API Reference](https://riftl.ink/api-reference): human-readable OpenAPI-backed reference
- [MCP Endpoint](https://api.riftl.ink/mcp): Rift Model Context Protocol server for agents
- [MCP Manifest](https://riftl.ink/.well-known/mcp.json): MCP Registry-style server metadata for Rift
- [MCP Docs](https://riftl.ink/docs/mcp): how agents should use the Rift MCP server
- [Health Check](https://api.riftl.ink/health): API status endpoint
- [Official X Profile](https://x.com/riftlinks): product announcements and public identity signal

## Use Cases

- Create deep links that work for both humans and AI agents
- Resolve a single link as a browser redirect or as structured JSON
- Attach machine-readable `agent_context` to links
- Track clicks, installs, attribution, and conversion events
- Expose link creation and management through MCP tools for LLM clients

## When To Use Rift

- Use Rift when an agent needs to generate or inspect deep links programmatically
- Use Rift when the same URL must serve browsers and AI clients differently
- Use Rift when attribution and conversion tracking need to stay tied to the link lifecycle
- Use Rift MCP for interactive agent workflows inside Claude, ChatGPT, or other MCP hosts

## When Not To Use Rift

- Do not use Rift as a general file store, CMS, or long-form content host
- Do not use Rift as an OAuth provider or identity platform
- Do not use Rift as a generic workflow engine unrelated to links, routing, or attribution

## Docs

- [Quick Start](https://riftl.ink/docs): CLI and manual setup paths to a working link in ~30 seconds
- [Manual Setup](https://riftl.ink/docs/manual-setup): raw HTTP setup path for developers and agents
- [Links](https://riftl.ink/docs/links): create, update, and resolve deep links
- [Attribution](https://riftl.ink/docs/attribution): click, install, and user attribution
- [Conversions](https://riftl.ink/docs/conversions): post-install event tracking
- [Webhooks](https://riftl.ink/docs/webhooks): outbound event delivery and signature verification
- [Deferred Deep Linking](https://riftl.ink/docs/deferred): route users into the app after install
- [Universal Links](https://riftl.ink/docs/universal-links): iOS and Android app-link setup
- [Domains](https://riftl.ink/docs/domains): primary and alternate custom domains
- [Apps](https://riftl.ink/docs/apps): registering iOS and Android apps
- [Publishable Keys](https://riftl.ink/docs/publishable-keys): client-side SDK keys
- [iOS SDK](https://riftl.ink/docs/ios-sdk)
- [Android SDK](https://riftl.ink/docs/android-sdk)
- [Web SDK](https://riftl.ink/docs/web-sdk)

## Authentication

- [Quick Start](https://riftl.ink/docs): create an account and get a Rift API key
- Authentication uses Bearer tokens with secret keys that start with `rl_live_`
- Client-side SDKs use publishable keys that start with `pk_live_`
- [Publishable Keys](https://riftl.ink/docs/publishable-keys): client-side SDK key management

## Agent Workflow

1. Discover the API at [OpenAPI JSON](https://riftl.ink/openapi.json) or [API Catalog](https://riftl.ink/.well-known/api-catalog)
2. Authenticate with a Bearer token using an `rl_live_` secret key
3. Create links with `POST https://api.riftl.ink/v1/links`
4. Resolve links with `Accept: application/json` when the caller is an agent
5. Use MCP at `https://api.riftl.ink/mcp` when the host supports MCP tools directly

## Constraints

- Secret keys are server-side credentials and must not be exposed in client code
- Publishable keys are limited to attribution and conversion endpoints
- Custom IDs require a verified custom domain
- Some workflows depend on mobile app setup, domain verification, or webhook receivers outside Rift

## Integrations

- [Webhooks](https://riftl.ink/docs/webhooks): click, attribution, and conversion events
- [MCP Endpoint](https://api.riftl.ink/mcp): create and manage Rift links from MCP clients
- [MCP Manifest](https://riftl.ink/mcp/server.json): machine-readable MCP server metadata
- [Apps](https://riftl.ink/docs/apps): iOS and Android app association setup

## Optional

- [Sitemap](https://riftl.ink/sitemap.xml)

## Scoped Context

# Riftl.ink Docs

Scoped documentation context for Riftl.ink developer docs.

## Primary Guides

- Quick Start: https://riftl.ink/docs
- Manual Setup: https://riftl.ink/docs/manual-setup
- Links: https://riftl.ink/docs/links
- Webhooks: https://riftl.ink/docs/webhooks
- Conversions: https://riftl.ink/docs/conversions
- Publishable Keys: https://riftl.ink/docs/publishable-keys
- MCP Server: https://riftl.ink/docs/mcp
- Official X profile: https://x.com/riftlinks

## When To Use

- Use these docs when setting up Riftl.ink manually or integrating specific product areas.
- Prefer the MCP guide when the host already supports MCP tools.
- Prefer the API reference when generating code from OpenAPI.


# Riftl.ink API

Scoped API context for Riftl.ink machine-readable integrations.

## Endpoints

- OpenAPI: https://riftl.ink/openapi.json
- Well-Known OpenAPI: https://riftl.ink/.well-known/openapi.json
- API Catalog: https://riftl.ink/.well-known/api-catalog
- MCP Endpoint: https://api.riftl.ink/mcp
- MCP Manifest: https://riftl.ink/.well-known/mcp.json
- Health: https://api.riftl.ink/health
- Official X profile: https://x.com/riftlinks

## Auth

- Bearer tokens use rl_live_ secret keys.
- Publishable keys use the pk_live_ prefix and are limited to attribution flows.

## Agent Guidance

- Use Accept: application/json when resolving links as an agent.
- Use MCP when the host supports native tool calling.


## Pricing

# Riftl.ink Pricing

Machine-readable pricing reference for Riftl.ink. This document is generated from the same tier data used by the website pricing UI.

## Summary

- Human checkout uses Stripe and monthly billing.
- Agent checkout is priced in USDC via x402 and is marked coming soon in the UI.
- Same product limits apply across the human and agent lanes.
- No surprise overage billing. Upgrade when you need higher limits.

## Tiers

### Free (`free`)

- Description: For prototyping
- Human price: $0
- Agent price: $0
- Link limit: 50 links
- Event limit: 10k events / mo
- Domain limit: 1 domain
- Recommended: no
- Enterprise-oriented: no

Features:
- Full REST API + MCP server
- iOS, Android & Web SDKs
- Deep links + deferred deep linking
- Install attribution + click tracking
- Custom styled QR codes with logos
- 30-day analytics retention
- Commercial use allowed

### Pro (`pro`)

- Description: For shipping
- Human price: $18 / month
- Agent price: $15 USDC / 30d
- Link limit: 2,000 links
- Event limit: 100k events / mo
- Domain limit: 5 domains
- Recommended: yes
- Enterprise-oriented: no

Features:
- Everything in Free
- Conversion tracking
- Webhooks on every event
- 1-year analytics retention
- Email support

### Business (`business`)

- Description: For scaling teams
- Human price: $55 / month
- Agent price: $47 USDC / 30d
- Link limit: 20,000 links
- Event limit: 500k events / mo
- Domain limit: 20 domains
- Recommended: no
- Enterprise-oriented: no

Features:
- Everything in Pro
- Unlimited team members
- 3-year analytics retention
- Priority email support

### Scale (`scale`)

- Description: For serious volume
- Human price: $199 / month
- Agent price: $169 USDC / 30d
- Link limit: 100,000 links
- Event limit: 2M events / mo
- Domain limit: Unlimited domains
- Recommended: no
- Enterprise-oriented: yes

Features:
- Everything in Business
- 5-year analytics retention
- Dedicated Slack channel

## Notes

- The website pricing section is the canonical product surface for plan presentation.
- This markdown file is intended for AI agents and comparison tooling.
- For the live pricing UI, visit https://riftl.ink/#pricing