Docs / CAMZA.AI
A production contract comes first.
Camza’s production API has not been published in this website release. The demonstration uses local sample data and illustrative event payloads. Before building an integration, obtain a versioned API contract covering authentication, supported operations, limits, errors and delivery behavior, then verify it in an approved test environment.
UPDATED
What an integration needs
- Base URL, API version and supported operations
- Authentication, permissions and credential rotation
- Request and response schemas, validation and error codes
- Rate limits, event ordering and idempotency
- A supported test environment and change policy
Use the sample for discussion
Illustrative event shape
A starting point for agreeing the data contract.
Delivery checklist
Questions about signing, retries and duplicate events.
No production endpoint, API key or documented service-level guarantee is implied.
A few useful questions.
Can I try this on my own cameras?
Start with a compatibility request. Share camera models, firmware and the event you want to find. An evaluation needs an agreed scope before any camera access is arranged.
Is the website demonstration a product benchmark?
No. The sample demonstration uses illustrative scenes and predefined events. It does not measure accuracy, response time or compatibility on your cameras.
What should we agree before a pilot?
Agree which streams are in scope, who can access the data, where processing runs, retention and deletion, expected outcomes, and the person responsible for reviewing results.
YOUR CAMERAS. YOUR CONTEXT.
Start with one
useful question.
A camera inventory. An event to find.
A clear next step for your team.