Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Feature flags

The crate ships one Cargo feature per API area, named after the area with underscores replaced by dashes:

AreaFeatureAreaFeature
account_apiaccountknowledge_bases_apiknowledge-bases
ai_agent_integrations_apiai-agent-integrationskubernetes_apikubernetes
ai_agent_skills_apiai-agent-skillslocations_apilocations
ai_agents_apiai-agentsmail_apimail
ai_gateway_apiai-gatewaymcp_apimcp
ai_gateway_inference_apiai-gateway-inferencenetwork_drives_apinetwork-drives
ai_models_apiai-modelspayments_apipayments
ai_solutions_apiai-solutionsprojects_apiprojects
apps_apiappsrouters_apirouters
balancers_apibalancerss3_apis3
cdn_apicdnservers_apiservers
container_registry_apicontainer-registryssh_apissh
databases_apidatabasesvpc_apivpc
dedicated_servers_apidedicated-servers
domains_apidomains
firewall_apifirewall
floating_ip_apifloating-ip
images_apiimages

The full feature turns every area on, and the default features are native-tls and full.

Compile a single area

timeweb-rs = { version = "0.9", default-features = false, features = ["native-tls", "servers"] }

Only the models the servers area uses are compiled — the other thousand models are left out. A model shared by two areas is compiled when either of them is enabled.

Check the names

The list above is generated from the specification. The authoritative list lives in the manifest, and the CI verifies that the manifest and the generated code stay in sync on every pull request.