Request FAQs

Question 1

Can I extract specific parts from JSON responses?

Accepted Answer

Absolutely. Request supports JSONPath queries, allowing you to precisely extract specific fields or sub-objects from optimized JSON payloads. This ensures your LLM only consumes the exact data it needs.

Question 2

What is Request and how does it help LLMs?

Accepted Answer

Request is a high-efficiency tool that optimizes web and API data before it reaches your Large Language Model (LLM), drastically reducing token consumption by 58-87%. This saves on costs, latency, and improves reasoning room.

Question 3

How does Request clean and optimize data?

Accepted Answer

For HTML, it strips navigation, ads, scripts, and converts content to clean Markdown. For JSON, it applies schema-first mode for large arrays, removes nulls/empties, strips URL templates, and deduplicates sub-objects.

Question 4

Does Request offer web search functionality?

Accepted Answer

Yes, Request includes a web search feature powered by DuckDuckGo. This functionality requires no API keys, making it easy to integrate for your LLM's data gathering needs.

Question 5

What kind of token savings can I expect with Request?

Accepted Answer

Based on benchmarks, Request can reduce token consumption by 58% for HTML content and up to 87% for JSON data. This translates to significant cost savings on popular LLM pricing tiers.

Request

Request

Key Features

Use Cases

Key Features

Use Cases