Use MomentIQ.dev with AI agents

MomentIQ.dev exposes a remote MCP server so AI agents can discover endpoints, estimate cost, create uploads, queue jobs, poll results, regenerate output URLs, and manage API keys without scraping the website.

Before the agent can use MomentIQ

The agent usually cannot connect itself just by visiting the website. First ask whether the agent supports remote MCP tools. If it does, connect the MCP URL below with a MomentIQ connector token from the dashboard. If it does not, ask the agent to use the REST API or SDK from backend code. If it cannot use tools or write backend code, use Moment Lab manually.

  1. Ask the agent: Can you use remote MCP tools?
  2. If yes, connect https://api.momentiq.dev/mcp.
  3. If no, tell the agent to build with the backend API or SDK.
  4. Keep the API key in server-side secrets only.
  5. Set a hard spend cap before running real processing jobs.

Remote MCP

MCP URL: https://api.momentiq.dev/mcp

Fallback URL: https://momentiq-production-7fdd.up.railway.app/mcp

Auth header: Authorization: Bearer <MIQ_CONNECTOR_TOKEN>

Direct connector setup

Copy this starter prompt

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 use the REST API from backend code.
MCP URL: https://api.momentiq.dev/mcp
Use MOMENTIQ_API_KEY from server-side environment variables only.
Never expose the key in browser code or public prompts.
Estimate cost and check account limits before creating processing jobs.

Recommended user flow

  1. Sign up at MomentIQ.dev dashboard.
  2. Create a scoped API key and set a hard spend cap.
  3. Give the key to the agent only through server-side environment variables or the MCP auth configuration.
  4. Ask the agent to run diagnostics, estimate cost, create an upload if needed, create a job, poll the job, and show the final output URL.

Agent-readable resources