IPFS Gateway API

Overview

The Leto IPFS Gateway is a comprehensive, lightweight, and fast API that respects your privacy. It enables access to IPFS content and offers a metric-based approach to analyze anonymous usage patterns.

The image below illustrates the structure of the Proxy Gateway Architecture:

Leto Gateway address

To switch from your current IPFS Gateway to Leto, all you need to do is change the gateway address used in your system to the Leto Gateway, available at https://leto.gg/ipfs/"cid".

Core Features

Here are the principal features offered by our IPFS Gateway:

• Anonymity: Our Gateway ensures you can access IPFS content without revealing your identity.

• Privacy: No logging of IP addresses or personal information.

• Performance: The Gateway is lightweight, fast, and easy to initialize.

• Metrics: We perform analyses based on the frequency and timing of CID requests.

Accessing IPFS via HTTP

Accessing IPFS data via HTTP is straightforward, particularly when utilizing an IPFS HTTP gateway. As a decentralized peer-to-peer network, IPFS simplifies data retrieval. We'll be using the Leto gateway in this guide, offering anonymous metrics alongside data provision.

Upon storing data using the web3.storage client, the put method returns an IPFS content identifier (CID) string. This CID corresponds to an IPFS directory containing files sent via the put method.

Here's how to leverage these CIDs:

• Point your application or program to the data in the Web3.Storage infrastructure using the respective CID.

Leto IPFS gateway compatibility

The Leto Gateway communicates with a range of services, ensuring content is served as swiftly as possible, regardless of the provider. Gateways we currently support:

• web3.storage

• ipfs.io

• dweb

• Cloudflare

Note: The w3link (https://ipfs.w3s.link/*) imposes a rate limit of 200 requests per minute per IP.