xyteThe Zyte API, on any proxy

Same request JSON, same response JSON, same error codes as Zyte's POST /v1/extract. Traffic exits through Oxylabs, Bright Data, ZenRows, any proxy URL, no proxy at all, or Zyte itself.

Get started

Migrating from Zyte

GitHub

🔌

Zyte-compatible

httpResponseBody, browserHtml, screenshot, actions, networkCapture, geolocation, sessions, cookies, markdown and Zyte's error types. Point existing Zyte code at it by changing the base URL.

What's covered

🌍

Any exit

Presets for 30+ proxy networks and scraping APIs, any http://user:pass@host:port, direct(), or Zyte as one more provider.

Providers

🔀

Fallbacks and routing

rotate, route per site, adaptive (learns which exit works where), circuit breakers, budgets and usage checks, with shared state in Redis.

Combining providers

🧭

Browser rendering

Playwright, patchright and other stealth forks, remote browsers, actions, network capture and captcha solvers.

Browser

🧠

AI extraction

product, article, jobPosting and customAttributes in Zyte's schemas, through any OpenAI-compatible LLM.

Extraction

🚀

Library, CLI or server

new Xyte().extract() in Node.js 22+ or Bun, xyte serve as a drop-in endpoint, a handler for Hono, Express or Next.js, or Zyte's proxy mode.

Deploying

Install

npm i @xtandard/xyte

import { Xyte, oxylabs, decodeBody } from '@xtandard/xyte';

const xyte = new Xyte({
  proxy: oxylabs({ username: process.env.OXYLABS_USERNAME!, password: process.env.OXYLABS_PASSWORD! }),
});
const page = await xyte.extract({ url: 'https://example.com', httpResponseBody: true, geolocation: 'US' });
console.log(decodeBody(page.httpResponseBody!));

Or as a server that existing Zyte code calls:

XYTE_PROVIDER=oxylabs OXYLABS_USERNAME=… OXYLABS_PASSWORD=… npx @xtandard/xyte serve --port 8011

Why it exists

xyte is a personal project: a library that makes one scraping flow easier to write. One request format for every exit, fallbacks from a cheap exit to a better one when a site bans, and the same code whether the request goes to Zyte, to a proxy, or nowhere special. It speaks Zyte's API because that API is well designed and well documented, so code moves between xyte and Zyte in either direction. It doesn't try to compete with or replace Zyte, which is one of its providers, and it isn't affiliated with Zyte (disclaimer).