@atcute/client

中文文档
5.1.2发布于 2026/09/100BSDES Module近 30 天下载 39.8万

lightweight and cute API client for AT Protocol

原始使用文档
文档目录11 节
  1. prerequisites
  2. usage
  3. making requests
  4. handling errors
  5. optimistic requests
  6. authenticated requests
  7. response formats
  8. runtime validation
  9. service proxying
  10. custom fetch handlers
  11. rate limiting

@atcute/client

lightweight and cute API client for AT Protocol.

npm install @atcute/client @atcute/bluesky

prerequisites

the client requires a definition package to know what queries and procedures are available. install one alongside the client:

npm install @atcute/client @atcute/bluesky

then register the type definitions using one of these methods:

// tsconfig.json
{
    "compilerOptions": {
        "types": ["@atcute/bluesky"],
    },
}
// env.d.ts
/// <reference types="@atcute/bluesky" />
// or as an import in your entrypoint
import type {} from '@atcute/bluesky';

now the XRPC methods will have full type information for the registered schemas.

available packages:

packageschemas
@atcute/atprotocom.atproto.*
@atcute/bluemojiblue.moji.*
@atcute/blueskyapp.bsky.*, chat.bsky.*
@atcute/frontpagefyi.unravel.frontpage.*
@atcute/germcom.germnetwork.*
@atcute/leafletpub.leaflet.*
@atcute/lexicon-communitycommunity.lexicon.*
@atcute/microcosmblue.microcosm.*, com.bad-example.*
@atcute/ozonetools.ozone.*
@atcute/pcktblog.pckt.*
@atcute/standard-sitesite.standard.*
@atcute/tangledsh.tangled.*
@atcute/whitewindcom.whtwnd.*

you can register multiple packages to combine their types.

usage

the client communicates with AT Protocol services using XRPC, a simple RPC framework over HTTP. queries are GET requests, procedures are POST requests.

making requests

import { Client, simpleFetchHandler } from '@atcute/client';
import type {} from '@atcute/bluesky';

// create a client pointing to the Bluesky public API
const rpc = new Client({ handler: simpleFetchHandler({ service: 'https://public.api.bsky.app' }) });

use get() for queries and post() for procedures. both return a response object with ok, status, headers, and data fields:

// queries use get()
const response = await rpc.get('app.bsky.actor.getProfile', {
    params: { actor: 'bsky.app' },
});

if (response.ok) {
    console.log(response.data.displayName);
    // -> "Bluesky"
}
// procedures use post()
const response = await rpc.post('com.atproto.repo.createRecord', {
    input: {
        repo: 'did:plc:1234...',
        collection: 'app.bsky.feed.post',
        record: {
            $type: 'app.bsky.feed.post',
            text: 'hello world!',
            createdAt: new Date().toISOString(),
        },
    },
});

handling errors

responses always include an ok field indicating success. for failed requests, data contains an error object with error (the error name) and optionally message (description):

const response = await rpc.get('app.bsky.actor.getProfile', {
    params: { actor: 'nonexistent.invalid' },
});

if (!response.ok) {
    console.log(response.data.error);
    // -> "InvalidRequest"
    console.log(response.data.message);
    // -> "Unable to resolve handle"
}

the error names are defined in the lexicon schema. you can switch on them for typed error handling:

if (!response.ok) {
    switch (response.data.error) {
        case 'InvalidRequest':
            // handle or account doesn't exist
            break;
        case 'AccountTakedown':
            // account was taken down
            break;
        case 'AccountDeactivated':
            // account deactivated by user
            break;
    }
}

optimistic requests

if you prefer throwing on errors instead of checking response.ok, use the ok() helper:

import { Client, ok, simpleFetchHandler } from '@atcute/client';

const rpc = new Client({
    handler: simpleFetchHandler({ service: 'https://public.api.bsky.app' }),
});

// throws ClientResponseError if the request fails
const profile = await ok(rpc.get('app.bsky.actor.getProfile', { params: { actor: 'bsky.app' } }));

console.log(profile.displayName);
// -> "Bluesky"

catch errors with ClientResponseError:

import { ClientResponseError } from '@atcute/client';

try {
    const profile = await ok(rpc.get('app.bsky.actor.getProfile', { params: { actor: 'invalid' } }));
} catch (err) {
    if (err instanceof ClientResponseError) {
        console.log(err.error); // error name from server
        console.log(err.description); // error message from server
        console.log(err.status); // HTTP status code
    }
}

authenticated requests

for password-based authentication, use PasswordSession from @atcute/password-session. it manages tokens, automatically refreshes expired access tokens, and can persist sessions:

npm install @atcute/password-session
import { Client, ok } from '@atcute/client';
import { PasswordSession } from '@atcute/password-session';

const auth = await PasswordSession.login({
    service: 'https://bsky.social',
    identifier: 'you.bsky.social',
    password: 'your-app-password',
});

const rpc = new Client({ handler: auth });

// requests are now authenticated
const session = await ok(rpc.get('com.atproto.server.getSession'));
console.log(session.did);
// -> "did:plc:..."

save auth.session to persist login across app restarts:

// after login, save the session
localStorage.setItem('session', JSON.stringify(auth.session));
// later, restore the session
const saved = localStorage.getItem('session');
if (saved) {
    const auth = await PasswordSession.resume(JSON.parse(saved));
    const rpc = new Client({ handler: auth });
}

use callbacks to keep persisted sessions in sync:

const auth = await PasswordSession.login(
    {
        service: 'https://bsky.social',
        identifier: 'you.bsky.social',
        password: 'your-app-password',
    },
    {
        onUpdate(session) {
            // called on login and token refresh
            localStorage.setItem('session', JSON.stringify(session));
        },
        onDelete(session) {
            // called on logout or session invalidation
            localStorage.removeItem('session');
        },
    },
);

response formats

by default, responses are parsed as JSON. for endpoints that return binary data, specify the format with as:

// get response as a Blob
const { data: blob } = await ok(
    rpc.get('com.atproto.sync.getBlob', {
        params: { did: 'did:plc:...', cid: 'bafyrei...' },
        as: 'blob',
    }),
);

// get response as Uint8Array
const { data: bytes } = await ok(
    rpc.get('com.atproto.sync.getBlob', {
        params: { did: 'did:plc:...', cid: 'bafyrei...' },
        as: 'bytes',
    }),
);

// get response as ReadableStream
const { data: stream } = await ok(
    rpc.get('com.atproto.sync.getBlob', {
        params: { did: 'did:plc:...', cid: 'bafyrei...' },
        as: 'stream',
    }),
);

// discard response body
await ok(
    rpc.post('com.atproto.repo.deleteRecord', {
        input: { repo: 'did:plc:...', collection: '...', rkey: '...' },
        as: null,
    }),
);

runtime validation

by default, responses are trusted without validation. for stricter guarantees, use call() with the schema from a definition package:

import { Client, ok, simpleFetchHandler } from '@atcute/client';
import { AppBskyActorGetProfile } from '@atcute/bluesky';

const rpc = new Client({
    handler: simpleFetchHandler({ service: 'https://public.api.bsky.app' }),
});

// validates params, input, and output against the schema
const response = await rpc.call(AppBskyActorGetProfile, {
    params: { actor: 'bsky.app' },
});

if (response.ok) {
    // response.data is validated
    console.log(response.data.displayName);
}

validation errors throw ClientValidationError:

import { ClientValidationError } from '@atcute/client';

try {
    await rpc.call(AppBskyActorGetProfile, { params: { actor: 'invalid!' } });
} catch (err) {
    if (err instanceof ClientValidationError) {
        console.log(err.target); // 'params', 'input', or 'output'
        console.log(err.message); // validation error details
    }
}

service proxying

service proxying lets you make authenticated requests through your PDS to other services. the PDS forwards the request with authorization headers proving it's acting on your behalf.

import { Client, ok } from '@atcute/client';
import { PasswordSession } from '@atcute/password-session';

// must be authenticated
const session = await PasswordSession.login({
    service: 'https://bsky.social',
    identifier: 'you.bsky.social',
    password: 'your-app-password',
});

// create a client that proxies requests through your PDS to the chat service
const chatClient = new Client({
    handler: session,
    proxy: {
        did: 'did:web:api.bsky.chat',
        serviceId: '#bsky_chat',
    },
});

// request goes to your PDS, which forwards it to api.bsky.chat with auth headers
const convos = await ok(chatClient.get('chat.bsky.convo.listConvos'));

common service IDs include:

  • #atproto_pds - personal data server
  • #atproto_labeler - labeler service
  • #bsky_chat - Bluesky chat service

custom fetch handlers

the simpleFetchHandler works for most cases. for advanced scenarios, provide your own handler:

import type { FetchHandler } from '@atcute/client';

const customHandler: FetchHandler = async (pathname, init) => {
    // pathname is like "/xrpc/app.bsky.actor.getProfile?actor=bsky.app"
    const url = new URL(pathname, 'https://public.api.bsky.app');

    // add custom headers, logging, retry logic, etc.
    console.log(`${init.method?.toUpperCase()} ${url}`);

    return fetch(url, init);
};

const rpc = new Client({ handler: customHandler });

or implement FetchHandlerObject for stateful handlers (like PasswordSession does):

import type { FetchHandlerObject } from '@atcute/client';

class MyHandler implements FetchHandlerObject {
    async handle(pathname: string, init: RequestInit): Promise<Response> {
        // your implementation
        return fetch(new URL(pathname, 'https://...'), init);
    }
}

const rpc = new Client({ handler: new MyHandler() });

rate limiting

retryFetchHandler wraps another handler to retry rate-limited (HTTP 429) responses. the delay comes from the Retry-After or RateLimit-Reset header when present, otherwise exponential backoff.

import { Client, retryFetchHandler, simpleFetchHandler } from '@atcute/client';

const rpc = new Client({
    handler: retryFetchHandler({
        handler: simpleFetchHandler({ service: 'https://bsky.social' }),
        maxRetries: 3, // attempts before giving up (default 3)
        maxDelay: 60_000, // upper bound on a retry delay, in ms (default 60s)
        fallbackDelay: 1_000, // backoff base when no header is present, or null to not retry (default 1s)
        shouldRetry: (response) => response.status === 429, // widen to retry other statuses
    }),
});

parseRateLimitHeaders reads the RateLimit-* headers off a response where they're exposed, returning null when they're absent or malformed:

import { parseRateLimitHeaders } from '@atcute/client';

const response = await rpc.post('com.atproto.repo.createRecord', {/* ... */});

const info = parseRateLimitHeaders(response.headers);
if (info) {
    console.log(`${info.remaining}/${info.limit} remaining, resets at ${info.reset.toISOString()}`);
}

版本与发布记录

@atcute/client 共发布 30 个版本,首次发布于 2024/08/18;过去 12 个月发布了 10 个版本。

版本发布日期距今
5.1.2latest2026/09/101 个月前
5.1.12026/06/304 个月前
5.1.02026/06/124 个月前
5.0.02026/05/095 个月前
4.2.22026/05/086 个月前
4.2.12026/01/0510 个月前

关于 @atcute/client 的常见问题

@atcute/client 是什么?

lightweight and cute API client for AT Protocol

如何安装 @atcute/client?

在项目目录运行 npm install @atcute/client,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:@atcute/lexicons(^2.0.0)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@atcute/client 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/atcute__client 是否存在。

@atcute/client 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@atcute/client 可以商用吗?

@atcute/client 使用 0BSD 许可。几乎没有限制:可自由使用、修改和分发,连保留版权声明也不要求。以上为概括,不构成法律意见,请以许可原文为准。

@atcute/client 的下载量有多少?

根据 npm 官方下载统计,@atcute/client 在 2026/10/07 – 2026/11/05 这 30 天内被下载 397,660 次,日均约 13,255 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@atcute/client 还在维护吗?

最新版本 5.1.2 发布于 2026/09/10(1 个月前);至今共发布 30 个版本,其中过去 12 个月发布了 10 个;首次发布于 2024/08/18。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。