Backblaze B2 Cloud Storage API

What authentication does the Backblaze B2 API use?

The B2 API uses HTTP Basic authentication for the initial /b2_authorize_account call, where the username is the application key ID and the password is the application key. This returns an authorization token and API URL used for all subsequent requests. Through Jentic, these credentials are stored encrypted in your Jentic One instance.

Can I upload files larger than 100 MB with the B2 API?

Yes. Files under 100 MB use the single-call /b2_upload_file endpoint. Larger files use the multipart flow: /b2_start_large_file to initiate, /b2_get_upload_part_url for each part URL, upload parts individually (minimum 5 MB each except the last), then /b2_finish_large_file to assemble. Maximum file size is 10 TB.

How do I list files in a B2 bucket through Jentic?

Search Jentic for 'list files in a Backblaze bucket' to load the /b2_list_file_names operation schema. Pass the bucketId and optional prefix/delimiter parameters to filter results. The endpoint returns up to 10,000 files per call with a nextFileName cursor for pagination. Install with pip install jentic.

What are the rate limits for the Backblaze B2 API?

B2 allows unlimited API calls for most read operations. Write operations are limited to approximately 100 calls per second per account. The /b2_authorize_account endpoint is limited to prevent brute-force attacks. The API returns HTTP 429 or 503 with a Retry-After header when limits are hit.

How does B2 pricing compare to other cloud storage providers?

B2 storage costs $0.006/GB/month - roughly one-quarter the price of AWS S3 Standard. Download bandwidth is $0.01/GB, and egress through CDN partners (Cloudflare, Fastly, Bunny) is free. There are no minimum storage durations or per-request charges for standard operations.

Can I limit what my agent is allowed to do with the Backblaze B2 Cloud Storage API?

Yes. Because you run Jentic One yourself, your own rules decide which B2 operations and credentials the agent can use, and scoping here is by operation since B2 write calls like /b2_upload_file and /b2_create_bucket carry the bucket and file details in the request body rather than the URL path. You can allow the agent only the operations it needs, such as /b2_get_upload_url and /b2_upload_file, and destructive ones like /b2_delete_bucket or /b2_delete_key stay excluded unless you add them. Your Backblaze application key ID and key are stored encrypted by your own instance and injected at execution time, so they never enter the agent's prompt or logs.