Request an API or SDK

Tell us which API or SDK you want the change feed to cover. We count the requests and curate against them.

Emendant only reports a breaking change that exists in its change feed. The feed covers the major AI SDKs today. If the thing that keeps breaking your code is not on that list, this form is how it gets considered.

An API does not have to be an npm package to be worth covering. If it is a package, naming it helps, and if it is an HTTP API with a dozen client libraries, say so in the notes.

The name you would say out loud. Required.

If an upgrade is what you are putting off, the version you cannot leave is the most useful thing here.

Optional, and up to 500 characters.

What happens next

Nothing automatic. Requests are counted, and the count is one of the things that decides what gets curated next. Covering an API means reading its published releases and writing an entry for each breaking change, by hand, so this is a signal rather than a queue.

New coverage arrives without a new release of the tool. When an entry is published,emendant feed update picks it up.

What this form records

What you type above, and a salted hash of your IP address, which exists so one person asking twice counts once. There is no field for your name or your email address, and the form sets no cookie. That means we cannot reply to a request: if you want an answer, write to contact@emendant.com instead, which the contact page describes. The privacy notice is the full account.

Something already covered, and wrong?

A finding you believe is false, or a missing break in a package the feed already describes, is a different and more urgent thing. Send it to contact@emendant.com, and include the output ofemendant explain <change-id> if you have it.