Open Issues Need Help
View All on GitHubAI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/entertainment/riddles`, to serve riddles with their answers and difficulty levels. The implementation involves creating a riddles package, building a collection of riddles, implementing the handler logic, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `/v1/entertainment/facts`, to serve random interesting facts. It will support optional category filtering and requires the development of a facts database and associated logic for random selection and testing.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue requests the implementation of a new API endpoint, `GET /v1/entertainment/jokes/dad`, to serve dad jokes. The implementation involves creating a new package, a service to fetch jokes from a data source (like icanhazdadjoke.com), an HTTP handler, tests, and updating endpoint costs. It's marked as a high priority and a critical launch item.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint to serve trivia questions with multiple-choice answers. It specifies two GET requests, one general and one with category and difficulty filtering, and outlines the expected JSON response structure. The tasks include creating a trivia package, building a database, implementing filtering and randomization, and adding tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue requests the implementation of a new API endpoint, `GET /v1/entertainment/chuck-norris`, which will return a random Chuck Norris fact. The implementation involves creating a handler, sourcing or creating a fact database, adding random selection logic, and writing tests, with a reference provided to an existing Chuck Norris facts API.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes to improve the holidays endpoint by normalizing the `country` parameter to uppercase before validation. Currently, the endpoint rejects lowercase country codes, leading to unnecessary validation errors for users. The fix involves a simple string transformation, enhancing user experience with minimal implementation effort.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This GitHub issue proposes a new API endpoint, `GET /v1/finance/bin/:bin`, to perform Bank Identification Number (BIN) lookups. The endpoint will return details such as the card's brand, type, category, issuing bank, and country. Key tasks involve creating a dedicated BIN package, setting up a BIN database, implementing card brand detection logic, and writing comprehensive tests.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint to generate Lorem Ipsum text. The endpoint will be configurable for the number of paragraphs and sentences, and the response will include the generated text, paragraph count, and word count. This is a straightforward implementation of a common utility function.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes adding a new API endpoint, GET /v1/places/time/:timezone, to provide the current time for a given timezone. The tasks involve integrating this functionality into the timezone package, implementing the time calculation, ensuring support for all timezones, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint to look up bank SWIFT/BIC codes. The tasks involve setting up a Swift package, integrating a SWIFT code database, implementing bank information retrieval, and adding tests for the new functionality.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of new API endpoints, `/v1/misc/dogs/fact` and `/v1/misc/dogs/image`, to provide dog facts and images. The implementation involves adding these to the animals package, integrating a dog facts database, connecting to a dog image API, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the addition of two new API endpoints, `/v1/misc/cats/fact` and `/v1/misc/cats/image`, to provide cat facts and images respectively. The implementation involves integrating with a cat facts database and a cat image API, along with adding tests and incorporating it into the animals package.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint for retrieving animal facts and information. It outlines two specific GET requests: one for a random animal fact and another for a specific animal's details. The tasks involve setting up a new package, a database for animal data, populating facts, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes adding a new API endpoint, `GET /v1/places/population/:country`, to retrieve population data by country and potentially city. The tasks involve integrating this into the 'countries' package, including historical data, and writing tests. It's labeled as a 'good first issue' and 'small size', indicating it's likely a straightforward addition.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint to check if an email address is disposable. The endpoint will require a package for checking, a database of disposable domains, a mechanism for updating this database, and comprehensive tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/health/cocktails`, to retrieve cocktail recipes and their ingredients based on a specified ingredient. The tasks involve setting up a new package, establishing a recipe database, implementing ingredient search functionality, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/entertainment/hobbies`, to provide random hobby suggestions. The implementation involves creating a new package, setting up a database for hobbies, enabling category filtering, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/entertainment/bucket-list`, to provide random bucket list ideas. The tasks involve setting up a new package, establishing a database for ideas, implementing category filtering, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/entertainment/jokes`, to serve general jokes, distinct from dad jokes. The implementation will involve creating a jokes package, supporting multiple joke categories, and including necessary tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue requests the addition of code examples for the SDK in several popular programming languages, including JavaScript/TypeScript, Python, Go, Ruby, and PHP, as well as a cURL example. The goal is to provide practical demonstrations of how to use the SDK.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue is a documentation task to create or improve the CONTRIBUTING.md file. The goal is to provide clear instructions for new contributors, covering aspects like development setup, the pull request process, code style, testing, and issue templates.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/transport/airports/:iata`, to retrieve airport information based on its IATA code. The task involves setting up an airports package, a database for airport data, implementing search functionality by city/country, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/transport/airlines/:iata`, to retrieve airline information based on its IATA code. The implementation involves creating a new package, setting up a database for airline data, and ensuring proper IATA/ICAO lookup and testing.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/transport/airports/:iata`, to retrieve airport information based on its IATA code. The implementation will involve creating an airports package, setting up an airport database, and adding search functionality by city/country, along with necessary tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/misc/universities`, to retrieve information about universities worldwide. The endpoint will support filtering by country and a general query parameter for searching. The response will include the university's name, country, city, website, and associated domains.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/transport/airlines/:iata`, to retrieve airline information based on its IATA code. The implementation involves creating a package, setting up a database for airline data, enabling IATA/ICAO lookups, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of new API endpoints for retrieving information about solar system planets. It defines two GET endpoints: one for a list of all planets and another for a specific planet by name, along with a sample JSON response structure. The tasks involve creating a new package, populating planet data, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/misc/universities`, to retrieve information about universities worldwide. The endpoint will support filtering by country and a general query parameter for searching. The required tasks include setting up a new package, establishing a university database, implementing search logic, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `/v1/misc/baby-names`, to retrieve baby names along with their meanings and popularity ranks. The endpoint will support filtering by gender and the starting letter of the name, and the response will include details like name, gender, origin, meaning, and popularity rank.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of new API endpoints to retrieve information about planets in a solar system. It outlines two GET requests: one for all planets and another for a specific planet by name, along with a sample JSON response structure. The tasks involve creating a dedicated package, populating planet data, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `/v1/misc/baby-names`, to provide baby names along with their meanings and popularity ranks. The endpoint will support filtering by gender and starting letter, and the response will include details about the name, gender, origin, meaning, and popularity.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/health/calories`, to calculate calories burned based on activity, duration, and user weight. The implementation involves creating a new package, a MET values database, the calculation logic, and associated tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint to retrieve public holidays for a specified country and year. The endpoint will return a list of holidays with their dates and names. The tasks involve setting up a holiday package, a multi-country database, implementing year filtering, and adding tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/health/calories`, to calculate calories burned based on activity, duration, and user weight. The implementation involves creating a new package, a MET values database, the calculation logic, and associated tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/places/countries/:code`, to retrieve detailed information about a specific country. The endpoint will return data such as name, capital, population, area, currency, and languages, and requires the creation of a new package, a country database, and associated tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/places/countries/:code`, to retrieve detailed information about a specific country. The endpoint will return data such as the country's code, name, capital, population, area, currency, and languages. The tasks involve setting up a new package, establishing a country database, sourcing flag URLs, and implementing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint to validate and parse IBAN (International Bank Account Number) numbers. The endpoint will accept an IBAN as a parameter and return a JSON object indicating its validity, country, bank code, and account number.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/tech/useragent`, designed to parse user agent strings. The endpoint will return structured data about the browser, operating system, device, and whether the request originates from a bot. The tasks involve creating a dedicated package, implementing parsing and detection logic, and adding tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `/v1/tech/useragent`, that will parse user agent strings. The endpoint will return structured data about the browser, operating system, device type, and whether the user agent represents a bot. The tasks involve creating a package, implementing parsing and detection logic, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `/v1/text/rhyme/:word`, to find rhyming words for a given input word. The implementation involves creating a rhyme package, developing a phonetic matching algorithm, building a rhyme database, and adding tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint to generate Lorem Ipsum text. The endpoint will allow users to specify the number of paragraphs and sentences, and the response will include the generated text, paragraph count, and word count. The tasks involve creating a package, implementing the generator, adding configurable length, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/tech/password`, to generate secure passwords. The endpoint will accept parameters for length, inclusion of uppercase letters, numbers, and symbols, and will return the generated password along with its length and strength.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `/v1/text/rhyme/:word`, to find rhyming words. The implementation involves creating a rhyme package, developing a phonetic matching algorithm, building a rhyme database, and adding tests. It's labeled as high priority and medium size.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint for fetching trivia questions. The endpoint will support filtering by category and difficulty, and will return questions with multiple-choice answers. The tasks involve setting up a trivia package, building a question database, implementing filtering and randomization, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint for emoji information and search. It outlines three specific endpoints: random emoji retrieval, searching by query, and retrieving a specific emoji by name. The implementation involves creating an emoji package, importing a database, and developing search and random selection functionalities, along with necessary tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue requests the implementation of a new API endpoint, `GET /v1/entertainment/chuck-norris`, that will return random Chuck Norris facts. The implementation involves creating a handler, sourcing or generating a fact database, implementing random selection, and writing tests. The provided reference API and labels suggest this is a straightforward task.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/entertainment/riddles`, that will return riddles with their answers and difficulty levels. The tasks involve setting up a riddles package, building a collection of riddles, implementing the API handler, and writing tests for the new endpoint.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue requests the implementation of a new API endpoint, `GET /v1/entertainment/jokes/dad`, to serve dad jokes. The implementation involves creating a new package, integrating a joke data source (like icanhazdadjoke.com), building an HTTP handler, writing tests, and updating endpoint costs. The task is marked as high priority and small in size.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `/v1/entertainment/facts`, to serve random interesting facts. The endpoint will support optional category filtering and should return a JSON object containing the fact, its category, and source. The tasks involve setting up a facts package, building a data source, implementing filtering and random selection logic, and writing tests.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue requests the implementation of a new API endpoint, `GET /v1/entertainment/chuck-norris`, that will return random Chuck Norris facts. The implementation involves creating a handler, sourcing or generating a fact database, adding random selection logic, and writing tests. The provided reference API and labels suggest this is a straightforward task.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue requests the implementation of a new API endpoint for dad jokes. It involves creating a new package, integrating a joke data source (either an external API or a custom collection), building an HTTP handler, writing tests, and updating configuration. The task is marked as high priority and small in size.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `GET /v1/entertainment/riddles`, that will return a riddle, its answer, and difficulty level. The tasks involve setting up a riddles package, building a collection of riddles, implementing the API handler, and writing tests for the new endpoint.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint to serve trivia questions with multiple-choice answers. It specifies the endpoint structure, expected response format, and outlines key tasks including database creation, filtering, randomization, and testing. The goal is to deliver this functionality within the first week.
🔱 One API key. Multiple enterprise-grade APIs.
AI Summary: This issue proposes the creation of a new API endpoint, `/v1/entertainment/facts`, to serve random interesting facts. The endpoint will support optional category filtering and requires the development of a facts database and associated logic for random selection and testing.
🔱 One API key. Multiple enterprise-grade APIs.