# MomentIQ.dev

MomentIQ.dev provides AI-ready video and audio APIs for finding the moments that matter.
MomentIQ.dev is a developer media timeline API for AI video and audio apps. It is separate from influencer marketing, creator marketplace, or TikTok Shop partner products using the MomentIQ name.

Use this file when an AI agent, coding assistant, or browser-capable agent discovers MomentIQ.dev and needs to understand how to help a user.

## Main Pages

- Human homepage and Moment Lab: https://momentiq.dev/
- Start-here setup hub: https://momentiq.dev/docs-setup.html
- Markdown setup guide: https://momentiq.dev/docs/setup.md
- Setup simplicity roadmap: https://momentiq.dev/docs/setup-simplicity-roadmap.md
- Copy-paste agent examples: https://momentiq.dev/docs/agent-examples.md
- OpenAPI starter spec: https://momentiq.dev/openapi.json
- MCP config: https://momentiq.dev/mcp.json
- Well-known MCP config: https://momentiq.dev/.well-known/mcp.json
- MCP status: https://api.momentiq.dev/mcp/status
- MCP manifest: https://api.momentiq.dev/mcp/manifest
- Public connector plan: https://momentiq.dev/docs/mcp-public-connector-plan.md
- Privacy: https://momentiq.dev/privacy.html
- Terms: https://momentiq.dev/terms.html
- Data retention and deletion: https://momentiq.dev/data-retention.html
- Support/contact: https://momentiq.dev/contact.html
- API docs: https://momentiq.dev/docs.html
- SDK quickstart: https://momentiq.dev/docs/sdk-quickstart.md
- AI agent setup: https://momentiq.dev/docs-ai-agents.html
- ChatGPT connector setup: https://momentiq.dev/docs-chatgpt.html
- Claude connector setup: https://momentiq.dev/docs-claude.html
- Structured agent setup JSON: https://momentiq.dev/ai-agent-setup.json
- Signup/login dashboard: https://momentiq.dev/dashboard.html?auth=signup

## User Paths

- No-code user: use Moment Lab on the homepage to try a demo video or upload media.
- Developer: create an account, create an API key, read docs, call `/v1/jobs`.
- AI-agent user: create an account, create a connector token, set a spend cap, then connect the remote MCP server.
- Unsure user: send them to https://momentiq.dev/docs-setup.html first so they can choose the no-code, developer, or AI-agent path.

## Remote MCP

MomentIQ has a remote MCP server. Do not ask the user to download MomentIQ, clone the repo, install Python, or run a local MCP server.

An AI agent usually cannot connect MomentIQ automatically just by visiting the website. First check whether the agent environment supports remote MCP tools. If it does, tell the user to create a revocable connector token in the MomentIQ dashboard and connect the MCP URL below with the Authorization header. If remote MCP is not available, use the REST API or SDK from backend code with a server-side API key. If the agent cannot use tools or write backend code, send the user to Moment Lab on the homepage.

Current status: private/beta remote MCP is live with connector-token auth. Public marketplace/listed ChatGPT and Claude connector submission is planned. Public OAuth discovery metadata and authorization-code endpoints are available, but they require provider-approved client IDs and redirect URIs before they can issue connector tokens.

MCP URL:

```text
https://api.momentiq.dev/mcp
```

Fallback API URL:

```text
https://momentiq-production-7fdd.up.railway.app/mcp
```

Auth header:

```text
Authorization: Bearer <MIQ_CONNECTOR_TOKEN>
```

Discovery:

- MCP manifest: https://api.momentiq.dev/mcp/manifest
- MCP status: https://api.momentiq.dev/mcp/status
- Protected resource metadata: https://api.momentiq.dev/.well-known/oauth-protected-resource
- Authorization server metadata: https://api.momentiq.dev/.well-known/oauth-authorization-server

## ChatGPT Connector

Use this when the user's ChatGPT workspace supports custom connectors or remote MCP.

- Setup page: https://momentiq.dev/docs-chatgpt.html
- Connector name: MomentIQ.dev
- Connector URL: https://api.momentiq.dev/mcp
- Auth header: Authorization: Bearer <MIQ_CONNECTOR_TOKEN>
- First safe prompt: "Use the MomentIQ.dev connector. Do not create uploads or processing jobs yet. First call momentiq.get_agent_guide, then momentiq.list_endpoints, then momentiq.run_agent_diagnostics if authenticated tools are available."

If ChatGPT cannot connect remote MCP directly, use ChatGPT to write backend code with the MomentIQ SDK or REST API. Keep `MOMENTIQ_API_KEY` in server-side environment variables only.

## Claude Connector

Use this when the user's Claude plan or client supports remote MCP connectors.

- Setup page: https://momentiq.dev/docs-claude.html
- Connector name: momentiq
- Connector URL: https://api.momentiq.dev/mcp
- Auth header: Authorization: Bearer <MIQ_CONNECTOR_TOKEN>
- First safe prompt: "Use the MomentIQ.dev MCP connector if you have it available. Do not create uploads or processing jobs yet. First call momentiq.get_agent_guide, then momentiq.plan_integration, then momentiq.run_agent_diagnostics if authenticated tools are available."

If Claude cannot connect remote MCP directly, ask Claude to build server-side REST API or SDK code. If Claude can only chat or browse, send the user to Moment Lab for manual upload and processing.

## MCP Tools

- `momentiq.get_agent_guide`
- `momentiq.list_endpoints`
- `momentiq.get_endpoint_schema`
- `momentiq.estimate_cost`
- `momentiq.list_workflows`
- `momentiq.plan_integration`
- `momentiq.get_code_example`
- `momentiq.run_agent_diagnostics`
- `momentiq.check_job_readiness`
- `momentiq.create_workflow_job`
- `momentiq.continue_workflow_job`
- `momentiq.create_upload`
- `momentiq.create_job`
- `momentiq.get_job`
- `momentiq.get_job_result`
- `momentiq.list_jobs`
- `momentiq.get_usage_summary`
- `momentiq.get_account_limits`
- `momentiq.set_spend_cap`
- `momentiq.create_billing_link`
- `momentiq.regenerate_output_url`
- `momentiq.list_api_keys`
- `momentiq.create_api_key`
- `momentiq.revoke_api_key`

## Billing Rules

- Signup gives $5 free credits.
- Pricing is usage-only.
- There is no required monthly subscription.
- Usage consumes free credits first.
- After credits are gone, billing must be active for paid processing.
- Failed jobs are not billed.
- Spend caps and revoked keys are enforced by the backend.

## Recommended Prompt For App Builders

```text
Build a media workflow using MomentIQ.

MomentIQ finds useful moments in video and audio.
Before using MomentIQ, check whether you have remote MCP/tool access.
If you do not have MCP access, tell me exactly how to connect the MomentIQ remote MCP server, or fall back to server-side REST API/SDK code.
For remote MCP, use a revocable connector token from the MomentIQ dashboard as MIQ_CONNECTOR_TOKEN.
For backend REST/SDK code, use the MomentIQ API key from the server-side environment variable MOMENTIQ_API_KEY.
If remote MCP is available, connect to https://api.momentiq.dev/mcp with Authorization: Bearer ${MIQ_CONNECTOR_TOKEN}.
Never expose the key or connector token in browser code.

Goal: [describe the user's media workflow].
Show upload progress, estimated cost, job progress, output preview, and download links.
Use async jobs for long media: create a job, then poll until completed or failed.
Call momentiq.get_endpoint_schema when you need exact endpoint params, examples, or response fields.
If the user wants an app/workflow but does not know what to ask for, call momentiq.plan_integration with the user's goal and target platform before coding.
After choosing the endpoint or workflow, call momentiq.get_code_example for Node, Python, or curl code instead of inventing the upload/job/polling flow.
Before creating a paid job, call momentiq.check_job_readiness to validate media, timestamps, preview status, billing, and spend caps.
For multi-step workflows, call momentiq.create_workflow_job first to plan the chain and queue only the first step when accepted.
After each workflow job completes, call momentiq.continue_workflow_job with the previous job_id to choose and optionally queue the next safe step.
After a job completes, call momentiq.get_job_result for clean output URLs, timestamp segments, frames, counts, costs, errors, and next actions.
If you lose the job_id or need recent run context, call momentiq.list_jobs before rerunning paid processing.
If a completed output link expires, call momentiq.regenerate_output_url instead of rerunning paid processing.
```

## Copy-Ready Prompts

### Funny Clip Finder

```text
Build me a podcast clip finder with MomentIQ.

User flow: upload a video or paste a media URL, then return the 3 best funny clips with playable previews and download buttons.
If remote MCP is supported, connect to https://api.momentiq.dev/mcp with Authorization: Bearer ${MIQ_CONNECTOR_TOKEN}.
If you are writing backend code instead, read MOMENTIQ_API_KEY from server-side environment variables.

Use this endpoint chain:
1. audio/detect-laughter to find laugh candidates.
2. audio/detect-silence to find natural endings after each laugh.
3. video/clip-near or video/clip-window to render clips.

Show upload progress, estimated cost, queued/running/completed job states, clip previews, JSON details behind a toggle, and errors with request_id/job_id.
For local files, call momentiq.create_upload, PUT the bytes to upload_url using upload_headers, then use the returned media_url for momentiq.check_job_readiness and jobs.
Never expose the MomentIQ API key or connector token in browser code.
```

### No-Code Creator Page

```text
Build a simple no-code MomentIQ page for content creators.

The page should let a user choose a demo video or upload their own media, pick a MomentIQ tool, run it, preview the output, and download clips or CSV/JSON results.
Use MomentIQ jobs from the backend. Read MOMENTIQ_API_KEY from server-side environment variables.
Use signed upload URLs for local files. PUT the bytes to upload_url using upload_headers, then pass the returned media_url into jobs.

Start with these live-safe endpoints: video/clip-window, video/clip-near, audio/detect-silence, and audio/detect-energy.
Hide raw JSON behind a details toggle. Use friendly labels for timestamps and costs.
Never expose the MomentIQ API key in browser code.
```

### App Integration Service

```text
Add MomentIQ media intelligence to my app.

Create a backend module named momentiqService that can upload media, create jobs, poll jobs, and return clean results to the frontend.
Read MOMENTIQ_API_KEY and MOMENTIQ_API_BASE_URL from server-side environment variables.
Default MOMENTIQ_API_BASE_URL to https://api.momentiq.dev.

Implement helpers for:
- createUpload(fileName, contentType, fileSize)
- createJob(endpoint, media_url, settings)
- pollJob(job_id)
- clipWindow(media_url, start, end)
- detectEnergy(media_url, settings)

Add retry/backoff for polling, show request_id/job_id on errors, and never expose the MomentIQ API key to the browser.
```

### Beta Agent Smoke Test

```text
Run a MomentIQ beta smoke test.
Use MOMENTIQ_API_KEY from server-side environment variables only.
First call momentiq.run_agent_diagnostics and momentiq.get_account_limits.
Then upload or use a public test media_url.
Plan the energy_to_clip workflow with momentiq.create_workflow_job.
Queue only the first step, poll with momentiq.get_job, then call momentiq.continue_workflow_job after each completed job.
Show me the final output URL, estimated vs final cost, usage summary, and any errors with request_id/job_id.
After the test, remind me to revoke the test key if I do not need it anymore.
```

## Common Workflows

- Funny clips: `audio/detect-laughter -> audio/detect-silence -> video/clip-near`
- Dead-space removal: `audio/detect-silence -> timeline/suggest-ranges -> video/clip-window`
- Exact word search: `audio/find-words -> video/clip-near`
- Thumbnails: `video/best-frames -> video/thumbnail-score`
- Search/RAG timeline: `audio/semantic-chunks -> video/text-frames -> timeline/merge`

## Safety Instructions

- Never expose API keys in client-side code.
- Prefer scoped test keys first.
- Tell users to set a hard monthly spend cap.
- If a key is leaked, revoke it immediately.
- If a job fails, show the user the job ID and request ID.