Your work.
Your tools.

Start with a search.

Public HTTP reads need no account. The TypeScript client validates requests and responses against the same contract as the API.

import { createClient } from '@artzine/sdk';

export async function findWork(baseUrl: string, query: string) {
  const client = createClient({ baseUrl });
  const { result } = await client.call('searchPublic', {
    query,
    medium: 'all',
    limit: 20,
  });
  return result;
}

Call findWork("https://artzine.com", 'light') with your search terms. The result contains work, artists, zines and subjects. Use next_cursor in the next search request to continue through the results.

Check current capabilities before preparing work. This response lists available presets and default limits. Read your account for its current limits and usage. Commands may also be temporarily restricted when admission is paused.

Connect a tool.

For a compatible MCP client, add this Streamable HTTP endpoint and complete the account authorization flow:

https://artzine.com/mcp

The MCP endpoint requires an authorized account, including for its reading tools. Choose the access the tool needs, then manage or disconnect it in Connected tools. OAuth clients can read the resource metadata to discover authorization settings.

For your own script, create a scoped API key in Connected tools and supply it through the client's token option, or as an HTTP Authorization: Bearer … header. Keep keys in your private runtime configuration. A distributed browser application should use an account authorization flow rather than embed a shared key.

Cross-origin browser requests are restricted. Use a server-side integration or a compatible authorized MCP client to connect your own tools.

Prepare, review, publish.

1. Read current capabilities and your account limits. Choose an available preset and an owned profile.
2. Prepare the work, then reserve its files. Request an upload grant for each slot.
3. Use the client's uploadDirect helper to send each file to the grant's storage endpoint. Keep the returned source version and pass it to complete the upload.
4. Read the preparation until processing completes. Review its actual preview, title, credits and permissions. Preparation and upload leave the work unpublished.
5. Publish the exact ready version after review. The returnedreceipt.resource_id identifies the work at /w/{id}. Keep that same address when updating the work; withdraw it when it should no longer be public.

File bytes go directly to storage. The API and MCP exchange metadata, versions and grants. Let background processing finish before publishing, and use the returned status when a format or file is refused.

For operations marked “Idempotency key required” below, supply an Idempotency-Key header, the client's idempotencyKey option, or an MCP idempotency_key. Keep the same key when retrying the same command with unchanged input. Use a new key for changed input. On a version conflict, read the current record and review your changes before retrying.

The client reports API failures as ArtzineApiError, with an HTTP status, structured error and request ID. Respect retry instructions and quota refusals. Additional response fields are accepted; required fields and known values remain validated.

One contract.

The HTTP API, typed client and MCP tools share the operations below. The OpenAPI document contains the complete request and response schemas. Account operations still enforce ownership and granted permissions.

Contract 0.1.0 · 56 operations

sha256:eea66c5812140736e839b2384202cefda1a5b6e4b5f3d93764a8ae87afe3fc78