feat: Add TOON (Token-Oriented Object Notation) support for efficient data serialization #82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Optimizes token consumption for structured and markdown data:
TOON Format Integration: Adds Token-Oriented Object Notation for
web_data_*tools, reducing tokens by 10-30% vs JSON while maintaining readabilityMarkdown Minification: Implements
remark+strip-markdownplugin forscrape_as_markdowntool, achieving 60% token reduction by removing base64 images, HTML tags, and formatting while preserving meaningful contentGoogle Search Response Sanitization: Cleanses search results by normalizing whitespace, removing Unicode formatting characters, deduplicating related keywords, and extracting only essential fields (link, title, description) from organic results (Thanks to Nikita for this valuable feedback | example response)
Changes
clean_google_search_payload()to sanitize and normalize search engine results(Still being tested and evaluated for efficiency)