Core API map

Audience: developers choosing the typed Java client.
Reference policy: generated Javadocs are canonical for signatures; source links are useful for snapshot development.

Need	Type	Module	Route
Configure HTTP/auth transport	ConductorClient / ApiClient	core	Javadocs
Start, query, pause, resume workflows	WorkflowClient	core	source
Poll and update tasks	TaskClient	core	source
Register task and workflow metadata	MetadataClient	core	source
Create schedules	SchedulerClient	core/Orkes clients	source
Manage schemas	SchemaClient	core/Orkes clients	source
Transfer workflow-scoped files	FileClient	core	guide
Emit SDK metrics	metrics integration	metrics	README
Compile, deploy, start, signal, and stream agents	AgentClient	core + AI	reference
Build/serve/run agents	AgentRuntime	AI	reference

OrkesClients assembles Orkes-specific typed clients from the shared transport. Use connection and authentication before constructing any client.

Next: workflows, agents, and compatibility.