AI SummaryA caching HTTP-to-HTTPS proxy for reference APIs that reduces costs and prevents rate limiting through intelligent caching and throttling. Developers building Copilot applications that depend on external reference data sources (ConceptNet, DBpedia, Wikidata) benefit most.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "reference-api-buddy — Copilot Instructions" prompt rules to my project. Repository: https://github.com/tinkermonkey/reference-api-buddy Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
A local caching request proxy designed for reference APIs where the data is non-secure and not changing frequently (conceptnet, dbpedia, wikidata, etc)
Reference API Buddy
A python module which provides an embeddable HTTP-to-HTTPS caching proxy that offers intelligent caching, progressive throttling, and detailed metrics to reduce API costs and prevent rate limiting.
Technology Stack
• Language: Python • Web Server: http.server.ThreadingHTTPServer • Database: SQLite or in-memory data structures • Test Framework: pytest
Code Structure
`text / ├── documentation # API and data model documentation | ├── requirements # High level requirements | ├── designs # Designs for requirements | ├── copilot # Reports and summaries generated by Copilot ├── reference_api_buddy # Core application code | ├── cache # Cache engine | ├── core # Core application logic | ├── database # Database models and manager | ├── security # Security manager | ├── throttling # Throttling manager | ├── utils # Utility functions | ├── cli.py # CLI entry point ├── pyproject.toml # Python dependencies ├── README.md # Project documentation ├── smoke_tests # Scripts for triaging overall functionality ├── tests # Unit tests | ├── unit_tests # Unit tests for individual components | ├── integration_tests # Integration tests for API endpoints | ├── performance_tests # Performance tests for APIs `
Code Style
• Don't create documentation files unless explicitly requested • All markdown reports and summaries other than README.md should be placed in the documentation/copilot directory • Always place all import statements at the top of the file. • Use snake_case for variable and function names. • Use CamelCase for class names. • Use triple double quotes for docstrings. • Minimize dependencies to only those that are absolutely necessary to minimize module size.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts