# Inspack

> Documentation for the Inspack (former GetGenAI) API, MCP server, and skills.

- [Introduction](https://docs.inspack.com/introduction.md): Build with Inspack — REST API, hosted MCP server, and skills.
- [Quickstart](https://docs.inspack.com/quickstart.md): Run your first content review in under five minutes.
- [Authentication](https://docs.inspack.com/authentication.md): How to authenticate against the Inspack API.
- [Public upload lifecycle and MCP migration](https://docs.inspack.com/public-upload-api.md): Initialize, upload, process for an intent, answer steering questions, and read organization-scoped asset artifacts.
- [MCP server overview](https://docs.inspack.com/mcp/overview.md): Connect AI clients to Inspack through the Model Context Protocol.
- [Connect a client](https://docs.inspack.com/mcp/connect.md): Add the Inspack MCP server to Claude Desktop, Cursor, or ChatGPT.
- [Available tools](https://docs.inspack.com/mcp/tools.md): Tools the Inspack MCP server exposes.
- [Skills](https://docs.inspack.com/skills/overview.md): Packaged Inspack workflows for AI agents. Coming soon.
- [API reference](https://docs.inspack.com/api-reference/introduction.md): REST endpoints exposed under /api/v1.
- [Allocate an upload version and backend signed PUT slots](https://docs.inspack.com/api-reference/upload/allocate-an-upload-version-and-backend-signed-put-slots.md): Customer org_id comes from authentication and overrides supplied values. System tokens require explicit org_id, in the init/process body or status query. Backend response bodies, status codes, and URLs are preserved. Upload operations consume no review credits. PUT every upload slot with all require…
- [Read upload status once and retrieve latest artifacts](https://docs.inspack.com/api-reference/upload/read-upload-status-once-and-retrieve-latest-artifacts.md): Supply asset_current_version in the query. Customer org_id comes from authentication and overrides supplied values. System tokens require explicit org_id in the query. Backend response bodies, status codes, and URLs are preserved. Upload operations consume no review credits. The portal adapts this r…
- [Retired - supply asset_current_version as a request parameter](https://docs.inspack.com/api-reference/upload/retired--supply-asset_current_version-as-a-request-parameter.md): Move to GET /api/v1/upload/asset/{asset_id} with asset_current_version in the query. This protected route returns HTTP 410 and performs no upstream work.
- [Retired - supply asset_current_version as a request parameter](https://docs.inspack.com/api-reference/upload/retired--supply-asset_current_version-as-a-request-parameter-1.md): Move to POST /api/v1/upload/asset/{asset_id}/process with asset_current_version in the JSON body and an optional ctx. This protected route returns HTTP 410 and performs no upstream work.
- [Retired - use POST /api/v1/upload/asset/{asset_id}/process](https://docs.inspack.com/api-reference/upload/retired--use-post-apiv1uploadasset-process.md): Processing is requested through /process with asset_current_version in the JSON body and an optional ctx; omitting ctx keeps the previous behaviour (full extraction for a review). This protected route returns HTTP 410 with the replacement and migration steps and performs no upstream work.
- [Process an uploaded version for an intent, or answer its steering question](https://docs.inspack.com/api-reference/upload/process-an-uploaded-version-for-an-intent-or-answer-its-steering-question.md): Supply asset_current_version in the JSON body. Omit ctx for a review upload (ctx.operation asset_for_review: previews, classification, panels where applicable, content). Send ctx {operation: inspector_extraction, inspector_type, on_question} to draft inspectors from a brief, master label, brand guid…
- [Retired - use POST /api/v1/upload/asset/init](https://docs.inspack.com/api-reference/upload/retired--use-post-apiv1uploadassetinit.md): Initialize with readable {filename, content_type, bytes}, PUT every returned upload slot with required_headers verbatim and no bearer token, start, then poll status. Follow any deduplicated version returned by start. Read latest.content.url using bearer authentication at /storage, or use MCP get_upl…
- [Review content and return inspector results and aggregated summaries](https://docs.inspack.com/api-reference/inspector/review-content-and-return-inspector-results-and-aggregated-summaries.md): Review shared objects with inspector_ids, recommendations and memory, or use typed ctx for finding questions and summaries. Includes blocks and conversation metadata. Customer organization_id comes from authentication; system tokens may supply it. Customer brand_id must belong to the authenticated o…
- [Retired - use POST /api/v1/inspector/review](https://docs.inspack.com/api-reference/inspector/retired--use-post-apiv1inspectorreview.md): Use inspector_ids: [id1, id2] and one shared objects list. Different-content batches require separate review requests. Review returns inspector_results and aggregated summaries together.
- [Retired - use POST /api/v1/inspector/review](https://docs.inspack.com/api-reference/inspector/retired--use-post-apiv1inspectorreview-1.md): Use inspector_ids: [id] and the same objects list. Review returns inspector_results and aggregated summaries together.
- [List inspectors linked to the caller's organization](https://docs.inspack.com/api-reference/inspector/list-inspectors-linked-to-the-callers-organization.md)
- [Retired - use POST /api/v1/inspector/review](https://docs.inspack.com/api-reference/inspector/retired--use-post-apiv1inspectorreview-2.md): Review returns inspector_results and aggregated summaries together. Standalone aggregation of supplied raw violations is retired; no aggregate-only mode exists. Summarize supplied findings using typed ctx.operation: summarize_findings and ctx.summaries; this differs from raw-violation aggregation.
- [Generate an Insights Report PDF](https://docs.inspack.com/api-reference/documents/generate-an-insights-report-pdf.md): Generates the server-side Insights Report PDF for a document the API caller can access.
- [Changelog](https://docs.inspack.com/changelog.md): Product updates and improvements to Inspack.

## OpenAPI Specs

- [json](https://app.inspack.com/api/v1/docs/json)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.