Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

analitiq-contract-models

The Analitiq authored contract models (Pydantic) — the write/input shapes for connectors, connections, endpoints, type-maps, streams, and pipelines. These are the single source of truth the published JSON Schemas (schemas.analitiq.ai) are generated from, packaged so the validator and the pipeline engine can validate documents against the contract directly (model_validate) instead of re-implementing its cross-field rules.

Install & use

pip install analitiq-contract-models
from analitiq.contracts.endpoints import ApiEndpointDoc
from pydantic import ValidationError

try:
    ApiEndpointDoc.model_validate(doc)   # structural + cross-field, offline
except ValidationError as exc:
    ...  # every contract rule, enforced from the one source

Importing needs no environment: the package defaults DOMAIN to the public contract host (analitiq.ai) before the models load.

What it ships

Analitiq's public contract surface — nothing internal.

The authored contract: the documents you write and Analitiq validates.

  • analitiq.contracts.connector — Connector
  • analitiq.contracts.connection — ConnectionInput
  • analitiq.contracts.endpoints — ApiEndpointDoc, DatabaseEndpointDoc, DatabaseObject
  • analitiq.contracts.type_map — TypeMapReadDoc, TypeMapWriteDoc
  • analitiq.contracts.stream — StreamInput (+ the endpoint refs)
  • analitiq.contracts.pipelines.config — PipelineInput
  • analitiq.contracts.credentials_file — CredentialsFile
  • analitiq.contracts.endpoint_identity — derive_db_endpoint_id
  • analitiq.contracts.shared — the shared building blocks those embed

The API contract: the request/response shapes of the public REST API.

  • analitiq.contracts.pipelines.data_sync — Data Sync API: PipelineRunRequest, the run/terminate/status responses, and the public run vocabulary (PublicRunStatus, PublicErrorCode)

Both are shape and rules only. Nothing here knows how Analitiq runs a pipeline, stores a run, or names a state internally — those live server-side and depend on this package, never the reverse. Internal persistence/catalog variants (*Document/*Config/*Patch/*Read, resolved-connector/catalog shapes, auth-state) are not included.

analitiq is a PEP 420 namespace shared with analitiq-validator.

Source of truth

These modules are the canonical Analitiq contract models — not a copy of them, and not rendered from one. The published JSON Schemas are generated from the same files, so the schemas and this package cannot drift: there is only one definition to drift from.

Versioning

analitiq-contract-models is a strict validator (extra=forbid, closed enums), so version bumps are coordinated: a consumer on an older minor rejects a newly-added field a producer emits. See the publishing/versioning notes in the source repo for the major/minor/patch semantics and the consumer rollout rule.

Metadata

Release files for analitiq-contract-models 1.0.0rc23

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for analitiq-contract-models 1.0.0rc23
File Size Uploaded
analitiq_contract_models-1.0.0rc23.tar.gz 250.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for analitiq-contract-models 1.0.0rc23
File Interpreter ABI Platform
analitiq_contract_models-1.0.0rc23-py3-none-any.whl Python 3 none any Details

Total release size: 512.4 kB

Release files / analitiq_contract_models-1.0.0rc23.tar.gz

Download URL analitiq_contract_models-1.0.0rc23.tar.gz
Size 250.4 kB
Tags Source
SHA-256 checksum
How to use checksums
9abcf2b3e480ef8ce09925fc69e1981c435da7d5a9e9be6ba5dc8ef616a0cd2c
BLAKE2b-256 checksum
How to use checksums
1ca75fc1cca053ef62a1e9bf1579e0a658336b2cf5240ef0b1398a8264c67f30
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 25, 2026.

Transparency log

Release files / analitiq_contract_models-1.0.0rc23-py3-none-any.whl

Download URL analitiq_contract_models-1.0.0rc23-py3-none-any.whl
Size 262.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
aa17388882a0fb5128f629bda2ff4398aef27ce623605a63258e54c7479e5aac
BLAKE2b-256 checksum
How to use checksums
aa9bf76618b0413a3f9f37575a2c7777c61c1503f02d099287be66d4a70a26e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 25, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page