Gemini webhooks for 1M-token contexts.

The timing problem

Long-context Gemini in a webhook handler

AnyHook ack-and-forwards. You run the Gemini call against your full corpus. No polling loop, no Redis queue, no Cloud Tasks.

import { verifyWebhook } from "@anyhook/verify";
import { GoogleGenerativeAI } from "@google/generative-ai";

const gemini = new GoogleGenerativeAI(process.env.GEMINI_API_KEY!);

export async function POST(req: Request) {
  if (!(await verifyWebhook(req, process.env.ANYHOOK_SIGNING_SECRET!))) {
    return new Response("invalid", { status: 401 });
  }

  const event = await req.json();

  // Run RAG over the full corpus. 45 seconds. Stripe doesn't care.
  const model = gemini.getGenerativeModel({ model: "gemini-1.5-pro" });
  const result = await model.generateContent([
    fullCorpusFor(event.payload.tenant_id),
    `Process: ${JSON.stringify(event.payload)}`,
  ]);

  await persistDecision(result.response.text());
  return new Response("ok", { status: 200 });
}

Questions teams ask

Does AnyHook support Gemini's webhook signature scheme?

Yes. Configure the Gemini signing secret as the source_secret for your app and AnyHook verifies inbound deliveries at the edge before forwarding.

What if my Gemini call hits a rate limit?

Return a 429 from your handler. AnyHook treats it as retriable, applies exponential backoff, and surfaces the retry chain in the dashboard. You can replay the original event once your quota resets.

Is this only for Gemini API webhooks, or also Vertex AI?

Both. Anything that sends signed HTTP webhooks works. AnyHook is provider-agnostic on the verification layer.