> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neynar.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Sponsor Signers
> Sponsor it yourself or let Neynar pay for it
### This guide builds on [Write data to Farcaster using Neynar managed signers](/docs/integrate-managed-signers). Useful to read that first if you haven't already.
There are two ways to sponsor a signer on behalf of a user. This saves the user from paying for it and increases conversion in your funnel. You have two options to sponsor:
You can choose to have Neynar sponsor the signer on your behalf, we will charge you credits that correspond to the sponsorship fees.
You can sponsor the signer directly. Your application must be signed up on Warpcast and have warps ≥ 100
## 1. Let Neynar sponsor it
Set `sponsored_by_neynar` to **true** as shown below, the rest will remain the same as in the parent [guide](/docs/integrate-managed-signers).
```typescript getSignedKey.ts theme={"system"}
const options = {
sponsor: {
sponsored_by_neynar: true
}};
const signedKey = await neynarClient.registerSignedKey(
createSigner.signer_uuid,
fid,
deadline,
signature,
options
);
```
When you see "sponsored by @your\_app\_fname" (@avneeshtest in this case) on the Warpcast screen, it's because you're signing a message. Even though it says "sponsored by @your\_app\_fname," the warps are being deducted from Neynar's account.
The signer is still branded under your name (@your\_app\_fname), Neynar is covering the costs and charging you credits in the background. The user is unaware of Neynar and thinks your app is covering the costs.
## 2. Sponsor it with your app
You can do this very easily, just follow the steps below!
Start by setting `sponsored_by_neynar` to **false**. Then, in the generate signature function add the following to generate a `sponsorSignature`:
```typescript getSignedKey.ts theme={"system"}
const sponsorSignature = await account.signMessage({
message: { raw: sigHex },
});
sponsor = {
sponsored_by_neynar: false,
signature: sponsorSignature,
fid: FID,
};
```
Then, add this sponsor object to the object we're returning like this:
```typescript getSignedKey.ts theme={"system"}
return { deadline, signature: sigHex, sponsor };
```
Finally, you can get the sponsor object from the `generate_signature` function and pass it in as an option in the `registerSignedKey` function like this:
```typescript getSignedKey.ts theme={"system"}
const { deadline, signature, sponsor } = await generate_signature(
createSigner.public_key
);
if (deadline === 0 || signature === "") {
throw new Error("Failed to generate signature");
}
const fid = await getFid();
const options = sponsor ? { sponsor } : undefined;
const signedKey = await neynarClient.registerSignedKey(
createSigner.signer_uuid,
fid,
deadline,
signature,
options
);
```
`signedKey` will have `signer_approval_url`. Make it available (either by creating a QR Code for the desktop application or allowing user to deeplink into warpcast by clicking on it in mobile device).
If you go ahead and try signing in now, it should show "Onchain fees sponsored by @xyz"
