socaity-schemas 0.0.1

Shared Pydantic schemas for APIPod services and clients: requests, responses, streaming chunks and provider transport envelopes.

socaity-schemas

Shared Pydantic models for APIPod services and their clients. One definition, used on both sides of the wire, so a service and a client never drift apart on field names or shapes.

Three groups:

• media_files: FileModel and its typed variants (ImageFileModel, AudioFileModel, VideoFileModel, ThreeDFileModel). The wire shape of a media-toolkit file: name, content type, and content as base64 or URL.
• schemas: OpenAI-compatible request and response models (chat, completion, embedding, image, video, audio, vision, 3D) plus streaming chunks (ChatCompletionChunk).
• transport: provider job envelopes (SocaityJobResponse, RunpodJobResponse, ReplicateJobResponse), their link/metric sub-models, and the StreamingResponse sentinel.
• service_definitions: registry models (ServiceDefinition, EndpointDefinition, ServiceAddress variants, parameter metadata) shared by APIPodRegistry and fastSDK.

from socaity_schemas import ChatCompletionRequest, ServiceDefinition, SocaityJobResponse
from socaity_schemas.service_definitions import RunpodServiceAddress

The schema shape mirrors the OpenAI API so OpenAI-compatible clients work without translation. That is about the wire format only: any provider (Flux, Whisper, ElevenLabs, in-house models) that matches the shape is a valid backend.

Install

pip install socaity-schemas

MIT-licensed.