Draft-only APITools + Posts

Send content to AiComing from external AI tools

Connect ChatGPT, Claude, automation platforms, scripts, or your own agents to create Tool and Post drafts. API-created content is never published automatically.

Manage API keys

Let an AI agent handle the complete workflow

Give the public Skill file to a compatible AI agent. It will choose Tool or Post, fetch valid categories and tags, upload a local image when needed, create the draft, and return review links.

Agent Skill

A procedural SKILL.md that an AI can read and execute without manually reconstructing the API flow.

https://aicoming.net/skills/submit-to-aicoming/SKILL.mdOpen file

OpenAPI 3.1

A machine-readable API definition for agents, GPT Actions, automation platforms, and generated clients.

https://aicoming.net/openapi.jsonOpen file

Give this instruction to your AI tool

The agent only needs the public Skill URL and your content. Provide the API key securely when the agent requests it.

Read https://aicoming.net/skills/submit-to-aicoming/SKILL.md and follow it to submit this content to AiComing as a draft. Ask me for an API key if AICOMING_API_KEY is not available.

How it works

The integration is intentionally simple and keeps publication under your control.

Create a key

Create an API key and save the plaintext value when it is shown.

Choose a resource

Use the Tool endpoint for directory listings or the Post endpoint for community content.

Send English JSON

Authenticate with a Bearer token and send the required English fields as JSON.

Review and publish

Open the returned preview URL, edit the draft if needed, and publish it manually.

Authentication

Send your API key in the Authorization header. You can revoke the key at any time from the API Keys page.

Authorization: Bearer YOUR_API_KEY

Draft endpoints

Choose the endpoint that matches the content you want to create.

Create a Tool draft

POST

Create a private AI tool directory listing owned by the API key's user.

Endpoint

https://aicoming.net/api/v1/tools/drafts

Required fields

name, website, description (maximum 100 characters)

Optional fields

content, categories (1–3 slugs or IDs), tags (up to 5 slugs or IDs), imageUrl. Content must be 50–50,000 characters when provided.

Example request

curl -X POST 'https://aicoming.net/api/v1/tools/drafts' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Example AI",
    "website": "https://example-ai.com",
    "description": "An AI assistant for research workflows.",
    "content": "A detailed English description with features, use cases, and pricing information.",
    "categories": ["productivity"],
    "tags": ["research", "writing"],
    "imageUrl": "https://example-ai.com/cover.png"
  }'

Successful response

Returns status draft plus editUrl and previewUrl. The preview route follows /settings/tools/{id}/preview.

Create a Post draft

POST

Create a private English community post owned by the API key's user.

Endpoint

https://aicoming.net/api/v1/posts/drafts

Required fields

title

Optional fields

description, content, category (slug or ID), imageUrl. Posts currently use one category; Tool drafts support both categories and tags.

Example request

curl -X POST 'https://aicoming.net/api/v1/posts/drafts' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "How AI changes research workflows",
    "description": "A practical overview for modern research teams.",
    "content": "## Introduction\n\nWrite the complete English post in Markdown.",
    "category": "ai-news",
    "imageUrl": "https://example.com/post-cover.png"
  }'

Successful response

Returns status draft plus editUrl and previewUrl. The preview route follows /settings/posts/{id}/preview.

Optional categories and tags

Use the returned slug values directly in categories and tags for Tool drafts, or in category for a Post draft. IDs remain supported for compatibility. Unknown or mismatched values return HTTP 400.

GET https://aicoming.net/api/taxonomies?type=category
GET https://aicoming.net/api/taxonomies?type=tag

Set or upload a cover image

Tool and Post drafts use the same imageUrl field. Choose a public URL or upload a local image first.

Option 1: use an existing image URL

Set imageUrl to a public HTTP(S) image URL. JPEG, PNG, WebP, GIF, and AVIF URLs are supported by the interface.

Option 2: upload an image with your API key

curl -X POST 'https://aicoming.net/api/v1/images' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -F 'file=@./cover.png'

Send one multipart file in the file field. The response returns url; copy that value into imageUrl when creating the Tool or Post draft. The configured size limit is capped at 10MB. Configure R2 storage for production; the local fallback is for development only.

Publication stays under your control

API keys have a deliberately narrow content-ingestion scope.

API keys can create drafts only. They cannot call the session-protected publish endpoints.

Tool and Post content should be English; Post locale is always stored as English.

Delete an API key immediately if it is exposed. Deleted keys stop authenticating.