Feed outside context into your MyInc workspace in minutes.

{
  "title": "Saved answer",
  "text": "This is the final summary worth keeping.",
  "tags": ["research", "launch"]
}

{
  "success": true,
  "data": {
    "id": "clip_123",
    "title": "Saved answer",
    "text": "This is the final summary worth keeping."
  },
  "error": null
}

• Good first endpoint for Hermes or your own agent.
• Works well for one final answer at a time.
• GET /api/agent/clips lists clips with clips:read.

{
  "items": [
    { "type": "url", "url": "https://example.com/article" },
    { "type": "markdown", "title": "Notes", "text": "# Key points\n- One\n- Two" }
  ]
}

{
  "success": true,
  "data": {
    "captureBatchId": "batch_123",
    "created": [
      { "id": "clip_1", "title": "https://example.com/article", "url": "https://example.com/article" },
      { "id": "clip_2", "title": "Notes", "url": null }
    ],
    "failed": []
  },
  "error": null
}

• Best starting point when an agent sends multiple items at once.
• Text, url, and markdown are all supported in one request (up to 50 items).
• This route charges AI credits per item and returns item-level failures when credits run out.

curl https://myinc.app/api/agent/upload \
  -H 'Authorization: Bearer tk_your_api_key' \
  -H 'Idempotency-Key: upload-001' \
  -F 'file=@notes.md'

{
  "success": true,
  "data": {
    "id": "clip_upload_123",
    "title": "notes.md"
  },
  "error": null
}

• Use this when your agent sends real files instead of plain JSON.
• Scoped keys and idempotency also work on uploads.
• This is the public agent facade over MyInc file upload, not the internal web route.

{
  "mode": "custom",
  "prompt": "Turn this page into a short publishable brief."
}

{
  "success": true,
  "data": {
    "jobId": "draft_123",
    "type": "page_generation",
    "status": "completed",
    "result": {
      "draftId": "draft_123"
    }
  },
  "error": null
}

• The generated draft stays pending your approval inside MyInc — nothing publishes automatically.
• Use this after clips are already organized into a page (POST /api/agent/pages, GET /api/agent/pages/:id).
• Poll GET /api/agent/jobs/:id for the draft status; generation consumes the same AI credits as the in-app flow.

{
  "name": "April launch plan",
  "template": "goal_milestones",
  "icon": "🚀"
}

{
  "success": true,
  "data": {
    "id": "project_123",
    "name": "April launch plan",
    "template": "goal_milestones"
  },
  "error": null
}

• Use this when the agent needs a long-lived workspace, not just one clip.
• Templates: goal_milestones or pipeline_board.
• Project creation follows the same plan-based active project limits as the main app.

{
  "stage": "clip",
  "referenceId": "clip_123"
}

{
  "success": true,
  "data": {
    "id": "project_item_123",
    "stage": "clip",
    "referenceId": "clip_123"
  },
  "error": null
}

• If columnId is omitted, MyInc resolves the first workflow column for that stage.
• Use this right after creating a clip or page when the agent is building a project workflow.