bucketjs.com valid

Bucket [](https://www.npmjs.com/package/bucket) [![tests](https://github.com/franciscop/bucket/workflows/tests/badge.sv

**Note:** The filesystem has no metadata store, so it ignores every option here except the content itself. Use the [Memory provider](#memory) when developing against metadata: it is the one provider that ignores nothing.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T13:47:45.798Z. Cached copy · Source on bucketjs.com

# Bucket [![npm install bucket](https://img.shields.io/badge/npm%20install-bucket-blue.svg)](https://www.npmjs.com/package/bucket) [![tests](https://github.com/franciscop/bucket/workflows/tests/badge.svg)](https://github.com/franciscop/bucket/actions) [![deps](https://img.shields.io/badge/deps-0-limegreen.svg)](https://github.com/franciscop/bucket/blob/master/package.json)

A small library to talk to any of the popular file storage solutions with a unified API:

```js
import { S3 } from "bucket"; // or R2, GCS, Azure, B2, FS, Memory

const bucket = S3("bucket-name", { id, secret });

const file = bucket.file("demo.txt");
await file.write("hello world");
console.log(await file.text());
```

Every provider behaves the same, so the code above works unchanged against any of them. That includes a "filesystem" bucket treating a local folder as a bucket, and an in-memory one for tests. Because they share an API, a file can be piped straight from one provider into another:

```js
// More complex example with streams and pipes
import { FS, S3 } from "bucket";

const local = FS("./public/");
const aws = S3("mybucketname", { id, secret });

const source = local.file("local.txt").stream();
const target = aws.file("newfile.txt").writable();
await source.pipeTo(target);
```

## Getting Started

First install the library:

```sh
npm install bucket
```

Then decide which bucket you're going to use, and grab its credentials. Put them in a gitignored `.env`, let's say S3, so put these variables:

```sh
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_BUCKET=
# Optional
AWS_REGION=
AWS_SESSION_TOKEN=
AWS_ENDPOINT_URL=
AWS_PUBLIC_URL=
```

Finally, you can import and initialize the library:

```ts
import { S3 } from "bucket";

// Read the variables automatically
const bucket = S3("bucket-name");

// Or inject them manually
const bucket = S3("bucket-name", {
  id: "...",
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=bucketjs.com · GET /v1/domain/bucketjs.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for bucketjs.com:
1. POST https://agentwebmap.com/v1/sites/bucketjs.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://bucketjs.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/bucketjs.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/bucketjs.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.