How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

DAZ 3D

Daz 3D is a Salt Lake City based 3D content and software company best known for Daz Studio, a free figure posing, morphing and rendering application, and for the Genesis line of morphable 3D human figures. The company runs a large first-party and marketplace store of 3D characters, clothing, props and environments, publishes the DSON (Daz Scene Object Notation) JSON-based scene file format, and licenses synthetic 3D character datasets for AI training through the surface that was formerly the Tafi brand. Its developer surface is an application SDK rather than a web API: a free C++ plug-in SDK, the DAZ Script ECMAScript scripting API documented in the public Daz Documentation Center, and open-source Daz-to-Blender / Unity / Unreal / Maya / Cinema 4D / 3ds Max bridge plug-ins published on GitHub. No public REST, GraphQL or event API is published.

human only

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles DAZ 3D the way a machine reads it — 3 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — DAZ 3D scores 33.1/100 (thin), with a separate agent-readiness read of 3/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Public but machine-unreadable

Why this profile is thin

Daz 3D publishes a complete, public DAZ Script API reference and its own DSON JSON file format spec as human-readable DokuWiki pages, but ships no OpenAPI, GraphQL SDL, AsyncAPI, Postman collection or JSON Schema anywhere — and api.daz3d.com, the only API-shaped hostname it owns, 302s every path to the marketing site root.

The documentation is public — a person can read it, but a machine cannot. This one is DAZ 3D's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.

What we probed
  • https://api.daz3d.com/openapi.jsonHTTP 302
  • https://www.daz3d.com/openapi.jsonHTTP 404
  • https://www.daz3d.com/rest/all/schema?services=allHTTP 404
  • https://docs.daz3d.com/public/dson_spec/startHTTP 200
  • https://www.daz3d.com/.well-known/agent-card.jsonHTTP 404

Checked 2026-08-12. If this is out of date, tell us on the provider's repo and we will re-run the profile.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 33.1/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 7.8 / 20
Commercial Clarity 15.3 / 20
Operational Transparency 2.7 / 13
Governance 1.5 / 12
Discoverability 5.7 / 10
Agent readiness — 3/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
DAZ 3D Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from DAZ 3D's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/daz-3d/"
   title="DAZ 3D on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/daz-3d.svg"
       alt="DAZ 3D Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile DAZ 3D

Each block below is one kind of artifact we hold for DAZ 3D. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Daz 3D Plans Pricing

3 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Daz 3D Rate Limits

0 limits

RATE LIMITS

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Daz 3D Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for DAZ 3D — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/daz-3d · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of DAZ 3D, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.