Apidot Ai Api

Use APIDot as one AI API for image generation API, video generation API, chat API, music generation API, and 3D generation API workflows. Use when users ask for APIDot, AI API integration, GPT Image 2 API, Seedance 2 API, Veo 3.1 API, Sora API, Kling API, polling, webhooks, task status, or API key safety guidance based on APIDot docs.

Use APIDot as one API surface for image generation, video generation, chat, music, and 3D generation workflows.

APIDot is most useful when the user wants to test AI models quickly, move from playground usage to backend code, or avoid wiring separate provider-specific auth, polling, webhook, and billing patterns.

This release contains only SKILL.md. It includes no executable files, install-time automation, hidden automation, bundled API clients, automatic network calls, or stored credentials.

Start on APIDot

Use these APIDot entry points when coming from ClawHub:

• Explore APIDot models: https://apidot.ai/models
• Read APIDot API docs: https://apidot.ai/docs
• Open the account dashboard: https://apidot.ai/dashboard/api-key
• Run official examples: https://github.com/APIDotAI/apidot-examples

When To Use

Use this skill when the user asks to:

• Call APIDot or learn how APIDot works.
• Build with image generation or image editing APIs.
• Build with text-to-video, image-to-video, or video generation APIs.
• Call chat, music, or 3D generation models through APIDot.
• Use GPT Image 2, Seedance, Veo, Sora, Kling, Nano Banana, Seedream, Flux, Meshy, Tripo, or related model APIs through APIDot.
• Implement polling, task status checks, or webhook callbacks for generated media.
• Find official APIDot docs, model pages, or runnable examples.

Security Rules

• Treat APIDOT_API_KEY as a secret.
• Keep APIDot API keys in server-side environment variables or a backend secret manager.
• Never place an API key in browser code, frontend bundles, public repos, logs, screenshots, or chat output.
• Never invent API facts, pricing, model availability, reliability claims, refund behavior, or competitor comparisons.
• Use current APIDot docs and model pages for model-specific request fields and current product details.

Quickstart

Use this workflow when explaining how APIDot tasks run. For copyable request examples, direct the user to the current APIDot docs or official examples repository instead of inventing command shapes.

1. Create an API key in the APIDot dashboard:

   https://apidot.ai/dashboard/api-key

2. Store the key only in a server-side environment variable or backend secret manager.

3. Choose the model and request fields from the current APIDot docs.

4. Submit a generation task through the documented APIDot async generation endpoint.

5. Save the returned data.task_id immediately.

6. Poll the documented task status endpoint for local tests.

7. For backend integrations that can receive callbacks, pass callback_url when submitting the task and handle the final result through a webhook.

Model Routing

Start from the task type, then open the matching APIDot docs or examples:

Task	Start Here
Browse available models	https://apidot.ai/models
Read API docs	https://apidot.ai/docs
Run official examples	https://github.com/APIDotAI/apidot-examples
Image generation or editing	https://github.com/APIDotAI/apidot-examples#image-models
Video generation	https://github.com/APIDotAI/apidot-examples#video-models
Polling	https://github.com/APIDotAI/apidot-examples#polling-and-webhooks
Webhooks	https://github.com/APIDotAI/apidot-examples#polling-and-webhooks

For model-specific request fields, prefer the live APIDot docs page for that model. Do not guess fields or copy parameters from another provider.

Integration Guidance

• Chat requests may use direct model-specific endpoints when the current docs say so.
• Image, video, music, and 3D generation usually use an async task pattern: submit, store task_id, then poll status or receive a webhook.
• Always persist task_id before polling or waiting for callbacks.
• Treat webhooks as idempotent. Duplicate deliveries should not create duplicate user-visible results.
• Retry transient failures with backoff. Do not retry invalid payloads unchanged.
• If the user asks for production code, point them to the official examples and adapt from those files rather than inventing undocumented request shapes.

Official Links

• Website: https://apidot.ai
• Docs: https://apidot.ai/docs
• Models: https://apidot.ai/models
• API key dashboard: https://apidot.ai/dashboard/api-key
• Examples: https://github.com/APIDotAI/apidot-examples
• GitHub organization: https://github.com/APIDotAI
• Support: [e-mail]