Updated for 2026: ESM3 developer API introduction using Biohub docs, supported SDK patterns, credentials and reliable error handling.
Use the maintained interfaces
Use the esm library and the current Biohub documentation. Existing examples may mention Forge class names because the API migrated to Biohub; verify exact imports in the version you install instead of inventing client methods.
Separate responsibilities
Keep API authentication and remote requests in a server-side service. The browser can communicate with your application backend, but must never receive the Biohub token. Use timeouts, capped retries with backoff and clear error reporting.
Design the request contract
Validate the shape and length of model inputs before sending; explicitly name the model and generation configuration in logs. Include request IDs when offered by the SDK. Be careful with sensitive research data, contracts, and permitted-use terms.
Confirm responses and costs
API responses can vary by model and version. Test against the official quickstart, instrument failure rates and time, and cap request volume. Retain reproducible experiment metadata without unnecessarily storing private sequence data.
Evidence and further reading
Primary sources: Biohub ESM3 model, Biohub maintained ESM repository, and Biohub learning resources. Check model cards and release notes for version-specific instructions.
Editorial note: Updated October 2026. Distinguish scientific literature and current product documentation from speculative applications; verify current API details before running code.