Add anthropic provider and refactor api field of publishJSON

[CahidArda]

Anthropic Provider

You can now publish requests to Anthropic API with

import { anthropic, Client } from "@upstash/qstash"

const client = new Client({ token: ... })
await client.publishJSON({
  api: {
    name: "llm",
    provider: anthropic()
  },
  body: {
    model,
  },
  callback,
});

Refactor

This PR is mainly concerned with how we handle the api field in publishJSON, batchJSON and enqueue:

await client.publishJSON({
  api: {
    name: "llm",
    provider: upstash()
  },
  body: {
    model,
  },
  callback,
});

Previously, the providers (upstash, openai, custom) returned the following object:

export type ProviderReturnType<
  TOwner extends Owner = Owner,
  TBaseUrl extends string = string,
  TToken extends string = string,
  TOrganization extends string | undefined = string | undefined,
> = {
  owner: TOwner;
  baseUrl: TBaseUrl;
  token: TToken;
  organization: TOrganization;
};

resend provider returned:

export type EmailProviderReturnType = {
  owner: "resend";
  baseUrl: "https://api.resend.com/emails" | "https://api.resend.com/emails/batch";
  token: string;
};

The publish request would be updated with this provider in a series of methods. Now there is a single method.

Now, the providers return LLMProvider and EmailProvider classes which extend BaseProvider. BaseProvider has some methods we utilize in getProviderInfo method.

getProviderInfo transform the api field of PublishRequest into ProviderInfo which is similar to the original ProviderReturnType:

export type ProviderInfo = {
  url: string;
  baseUrl: string;
  route: string[];
  appendHeaders: Record<string, string>;
  owner: Owner;
};

Notive the appendHeaders. Now, the headers are created in the BaseProvider and it's subclasses, instead of appendLLMOptionsIfNeeded and appendAPIOptions .

[linear]

DX-1323 qstash llm anthropic support

[fahreddinozcan]

I feel like Owner is not the correct keyword here, because EmailOwner or LLMOwner feels like referring to a user, not a company. I was thinking of Provider at first, but we already use that for classes. Can we think of sth else?

[CahidArda]

I took the owner from the old api. It's not the best name but I couldn't think of a better alternative. Something like ProviderOwner would be too much I think

[fahreddinozcan]

Can we check if the owner is openai?

[fahreddinozcan]

Can we seperate the utilties?

[CahidArda]

you mean different files right?

[fahreddinozcan]

yup

[CahidArda]

moved them to utils.ts