Build: integrate Polimake

Polimake combines a web product for creative teams with an integration layer designed to connect files, semantic search, AI analysis, and approval workflows with external tools.

This section is written for developers, integrators, and AI agents who need to understand Polimake as a technical system, not just as a marketing tool.

API Status

Polimake's public API should be treated as preview/beta until the team publishes production credentials, limits, and contracts. The examples in this section describe the recommended contract for integrations, but they may change before general availability.

If you need access to a real integration, contact the Polimake team through the developers page or the usual sales channels.

What You Can Integrate

• Media objects: files, images, videos, documents, and associated metadata.
• Semantic search: find resources using natural language, not just by filename.
• AI analysis: tags, descriptions, objects, scenes, suggested uses, and other metadata fields.
• Projects: separate asset repositories by client, brand, campaign, or team.
• Webhooks: react to uploads, completed analyses, status changes, and approvals.
• Internal agents: connect Polimake with CRMs, CMSs, intranets, sales tools, or private copilots.

Core Concepts

Project

A project groups files, permissions, searches, workflows, and business context. For an agency, it usually maps to a client or account. For a company, it can map to a brand, department, or internal repository.

Media object

A media_object represents a creative asset: image, video, audio, document, presentation, or related resource. It includes technical metadata, preview URLs, tags, AI analysis, permissions, and status.

Semantic search

Semantic search lets you make queries like:

presentation for a renewable energy client with results charts

Instead of relying solely on filenames or folders, Polimake searches by meaning, descriptions, tags, visual content, and project context.

AI analysis

AI analysis extracts useful fields for organizing and reusing assets:

• Natural description of the content.
• Objective, aesthetic, and conceptual tags.
• Detectable objects, scenes, people, or logos.
• Recommended uses.
• Risks or review notes if configured.

Base URL

The examples use this preview URL:

https://api.polimake.com/v1

Quick Example

curl https://api.polimake.com/v1/media/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "project_id": "brand-assets",
    "query": "logo sobre fondo blanco",
    "top_k": 10
  }'

Resources for Agents

• Developer hub: /build
• General documentation: /docs
• OpenAPI preview: /openapi.json
• Agent summary: /llms.txt

Next Steps

Start with Authentication, review the media object model, and try the semantic search contract.

To explore this topic further, see Webhooks.