llm-api-contract

To correctly call LLMService completion endpoints in TypeScript, pass messages to the complete method and access the returned response.content and response.usage.estimatedCost fields to prevent compile-time and runtime errors.

The correct LLMService response field names for structured completion and streaming are content, stopReason, and usage.estimatedCost. Accessing these exact fields prevents incorrect data extraction and runtime failures.

Effect-based error handling for LLMService API calls enforces specific error semantics during method execution. This contract ensures TypeScript agent layers correctly catch and manage failures without mismatched error types.

Yes, you can use this TypeScript LLMService contract for embedding and token counting. It specifies exact API signatures for the embed and countTokens methods to ensure non-compiling calls are prevented.

Your TypeScript LLMService code fails to compile when calling getModelConfig because the method signature does not match the defined API contract. Validating parameter shapes against the contract prevents these build errors.

You need an API contract for LLMService test provider scenarios when building deterministic tests. It codifies exact method signatures and field names to ensure test mocks accurately reflect production LLM behavior.