Virlo Comet endpoint migration reference

Review deprecated recurring research routes alongside the current content research agent model.

What to build with it

  1. Find existing schedules and decide which should continue.
  2. Create an equivalent recurring agent and review cadence and autonomy explicitly.
  3. Stop the old schedule after verifying the replacement to avoid duplicate collection and billing.

Provider reference: Virlo documentation. Authentication uses a provider-issued Bearer token, stored on your server.

Endpoints and inputs

19 documented operations. Query and path fields are listed separately from JSON request-body fields.

Before you integrate

  • These routes are deprecated. Do not assume historical Comet IDs can be used as current agent IDs.

Check the provider's current price, allowed use and retention terms before sending requests. An optional field can be absent; the schema alone does not establish its completeness or accuracy.

Give this task to your coding agent

virlo-comet-migration agent prompt
Help me implement virlo comet endpoint migration reference using the documented Virlo API.

Reference: https://allthemapis.com/social-media-apis/virlo-comet-migration
Provider documentation: https://dev.virlo.ai/docs/comet
Base URL: https://api.virlo.ai
Starting operation: POST /v1/comet

Read the current provider docs and confirm the required inputs before writing code. Load VIRLO_API_KEY from a server-side environment variable and use Bearer authentication. Do not put the key in client code, logs, analytics, or the chat.

Ask me for any missing video URL, creator handle, research intent, or job ID. Do not invent a result. Ask for approval before starting billable lookups, recurring jobs, or destructive changes. For jobs, keep the returned ID and poll with the documented delay instead of starting the job twice. Handle pagination, rate limits, partial results, and missing fields explicitly.

Build the smallest integration for this task:
1. Find existing schedules and decide which should continue.
2. Create an equivalent recurring agent and review cadence and autonomy explicitly.
3. Stop the old schedule after verifying the replacement to avoid duplicate collection and billing.

Return the code, the environment variables I need, and a short explanation of what was actually retrieved versus inferred. Do not execute paid requests until I approve.

Sources and review dates

Virlo's public documentation and OpenAPI schema reviewed October 27, 2026. Endpoint paths and field names below refer to that provider's API. This is an integration reference, not a measured performance ranking.

Corrections: email faizank@docsalot.dev with an official source.