# 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)