0.13 FAQ

​

What’s changing with SDK 0.13?

SDK 0.13.0 introduces weight separation so models/weights are handled separately from the SDK package. All changes are also described in the changelog and further information for our Python release is provided in the Python Migration Guide.

​

Do I have to upgrade to SDK 0.13?

Yes, support for SDK versions 0.12 and below will end on March 31, 2026.

​

Will my existing key stop working?

Yes, on March 31, 2026. Until then, your existing key continues to work with SDK versions 0.12.0 and below. Plan to update to the latest SDK version accordingly.

​

When do I need to generate a new key?

You need a new key only if you upgrade to SDK 0.13 or later. Use the developer portal’s key management once the new flow is published.

​

Can I use a new 0.13 key with an older SDK version?

No. An old SDK with a new key will not work. New keys only work with SDK 0.13 and above.

​

Can I use an old key with SDK 0.13?

No. SDK 0.13 requires a new key generated in the developer portal after the 0.13 rollout.

​

Why did my keys “disappear” in the developer portal?

After the rollout, the portal shows keys from the new system. Previously generated keys are not migrated, so they do not appear in the 0.13 key list. This does not mean your old keys stopped working—they remain valid for older SDK versions until March 31, 2026.

​

Why aren’t old keys migrated automatically?

Keys are stored securely (hashed). The new service uses a different hashing configuration, and migrating keys would require operational work and security trade-offs. Given current usage, we chose the safer and simpler approach: generate a new key for SDK 0.13.

​

How do I know which SDK version I’m using?

• Check your dependency lockfile (for example, Cargo.lock, poetry.lock, or package-lock.json).
• If available, run your package manager’s version command (for example, pip show aic-sdk, npm ls aic-sdk, or cargo tree | grep aic-sdk).

​

What error will I see if my key and SDK version don’t match?

You will see a license version unsupported error. Troubleshoot in this order:

1. Confirm your SDK version (see above).
2. Confirm you are using the matching key type:
   • Old SDK → old key
   • SDK 0.13+ → new key
3. If needed, regenerate a new 0.13 key in the developer portal and retry.

​

Does this affect offline usage?

No change is intended with this rollout. If your setup previously worked in environments with limited connectivity, it should behave the same. Future authentication improvements may change this; we will communicate ahead of time.

​

Do I need to update my integration code?

If you upgrade to 0.13, expect to update your integration because the release is a major version with breaking changes, especially around weight separation and API behavior. All changes are also described in the changelog and further information for our Python release is provided in the Python Migration Guide.

​

What about the Pipecat integration?

We are currently working on updating our Pipecat integration to v2.0. Please check back here for updates.

​

Who should I contact if I’m stuck?

If you run into issues upgrading or generating keys, open a ticket with support and include:

• SDK version
• language bindings version
• error message with logs
• environment details (OS and architecture)

​

Is there a rollback plan if upgrading breaks my pipeline?

Yes:

• You can stay on your current SDK version and keep using your old key.
• Pin your dependency to the previous version and redeploy. Remember that older SDK versions are supported only until March 31.