Resource Reference

The render lexicon ships 14 top-level resources. Each maps to a Public API create body; follow the reference link for the underlying API shape.

Resource	Type	Group	Create	Reconciled by	Marker	API reference
WebService	Render::Services::WebService	Services	POST /services	name	yes	reference
StaticSite	Render::Services::StaticSite	Services	POST /services	name	yes	reference
PrivateService	Render::Services::PrivateService	Services	POST /services	name	yes	reference
BackgroundWorker	Render::Services::BackgroundWorker	Services	POST /services	name	yes	reference
CronJob	Render::Services::CronJob	Services	POST /services	name	yes	reference
Postgres	Render::Datastores::Postgres	Datastores	POST /postgres	name	—	reference
KeyValue	Render::Datastores::KeyValue	Datastores	POST /key-value	name	—	reference
EnvGroup	Render::Config::EnvGroup	Config	POST /env-groups	name	yes	reference
Project	Render::Projects::Project	Projects	POST /projects	name	—	reference
Environment	Render::Projects::Environment	Projects	POST /environments	name + project	—	reference
Disk	Render::Services::Disk	Services	POST /disks	name + service	via service	reference
CustomDomain	Render::Services::CustomDomain	Services	POST /services/{serviceId}/custom-domains	name	via service	reference
RegistryCredential	Render::Config::RegistryCredential	Config	POST /registrycredentials	name	—	reference
Webhook	Render::Config::Webhook	Config	POST /webhooks	name	—	reference

Property types such as WebServiceDetails, StaticSiteDetails, CronJobDetails, NativeEnvironmentDetails, DockerDetails, Image, ServiceDisk, Route, Header, ReadReplica, and CidrBlockAndDescription are authored inline on a resource and are documented alongside the resources they belong to.

Cross-resource references

Render assigns ids on create, so id-valued fields accept the declared resource in place of a string: Disk.serviceId, CustomDomain.serviceId, Environment.projectId, *.environmentId, EnvGroup.serviceIds, Image.registryCredentialId. Attribute reads on datastores (internalConnectionString, externalConnectionString, psqlCommand / cliCommand) resolve from the live /connection-info endpoint; id, dashboardUrl, and the other response fields resolve from the live resource.

Ownership

Services and env groups carry chant’s marker in their env vars. Disks and custom domains have no marker but hang off a service and inherit its verdict (the service boundary), so an undeclared disk or domain under a chant-owned service is pruned too. Datastores, projects, environments, registry credentials, and webhooks have no marker channel and no boundary: their ownership verdict is unknown, and they are removed only by an explicit renderDelete of a plan that names them.