Find the right API for your next build. Give your AI agent the same evidence.
Discover thousands of public APIs, compare health and trust signals, and monitor the ones your projects depend on. Reqistry brings API research to your phone—and the same catalog to your AI coding agent through MCP (Model Context Protocol).
Browse the catalog · Documentation · Star this repo · Report an issue
5K+ downloads on Google Play as of October 2026. Free, ad-supported Android app. No subscription.
Your API research, project stack, and monitoring in one place. Go from “Which API should I use?” to a shortlist you can compare, save, and keep watching.
Give each build its own project: a finance dashboard, a travel app, or your next AI tool. Group its APIs together, keep favorites synced, and turn on project monitoring for a daily health digest and health-history snapshots. Pick up your research with the context already organized.
Follow keywords that matter to your work. Get push alerts when matching APIs are added or change, including pricing and trust updates. Watch a topic such as weather, payments, or AI while you focus on building.
Reqistry's hosted service runs scheduled health checks around the clock. Inspect observed availability, response times, and uptime history; enable alerts for saved APIs when health, pricing, or trust changes. The registry change feed puts changes across the catalog in one place.
Checks are periodic—roughly hourly according to the monitoring documentation—with verification timestamps on API profiles.
Select 2–8 APIs inside the app and compare trust, pricing, authentication, response time, 30-day uptime, rate limits, SDKs, and OpenAPI availability where recorded. Get an evidence-based top pick, see the fastest option and strongest uptime, and revisit recent comparisons without rebuilding your shortlist.
Bring Reqistry into Claude Code, Cursor, Codex, or another compatible AI client. Describe what you need, ask your agent to compare candidates, inspect their health evidence, and find alternatives using the hosted MCP tools. Manage agent keys from the app's Settings. Connect your AI agent →
In-app AI-powered decisions are marked “coming soon” in the current codebase. The available in-app Intelligence workflow is evidence-based comparison; natural-language AI interaction with the catalog currently runs through connected MCP clients.
Open Intelligence → Curated collections, pick a job, and jump straight into comparison. Current presets include:
| Collection | What it helps you explore |
|---|---|
| Build a finance dashboard | Finance and cryptocurrency APIs for market data and financial tools. |
| Best free AI APIs | AI and machine-learning APIs with free or freemium access. |
| APIs for travel apps | Weather, travel, transportation, and geocoding APIs. |
| No-auth APIs for prototypes | Free APIs you can try without setting up an API key. |
Built an API—or found one worth sharing? Submit it from the app for review, then follow its review status under My submissions. Help developers and AI agents discover useful APIs through the same catalog.
Search thousands of APIs across AI, finance, weather, maps, security, games, and more. Filter by pricing, authentication, and CORS support, then inspect documentation and verification signals before adding an API to your stack.
Health and trust signals help you evaluate an API using available evidence. Check the verification timestamp and provider documentation when making an integration decision. How trust scoring works →
Screenshots from the app's Google Play listing assets:
| Discover your next API | Inspect health and trust | Search and filter |
|---|---|---|
 |
 |
 |
Your coding agent can research APIs using Reqistry's catalog and health evidence during your development session. Connect it through the hosted MCP server:
https://mcp.reqistry.dev/mcp
Follow the MCP installation guide for Claude Code, Cursor, OpenAI Codex, OpenCode, Windsurf, and other compatible clients. Public catalog discovery requires no account or API key; the app also provides agent-key management in Settings.
Once connected, try:
Find a free weather API with no authentication. Check its health and CORS support.
Compare APIs for sending transactional email, including pricing and authentication.
Find alternatives to this API and show the evidence behind your shortlist.
| Use Reqistry through | Start here |
|---|---|
| Android — discover, save, and monitor on the go | Google Play |
| Web — browse and compare in your browser | reqistry.dev |
| AI agents — query the catalog through MCP | Connect your agent |
| REST API — work with the catalog as JSON | API reference |
Try a public read from your terminal:
curl --fail --show-error https://api.reqistry.dev/v1/categoriesThis repository contains the Flutter mobile app. The web catalog, REST API, and MCP server are hosted Reqistry services.
- Star this repository if Reqistry belongs in your developer toolkit.
- Try the app and leave an honest review on Google Play.
- Share it with your team or a developer choosing APIs for their next project.
- Grow the catalog by submitting an API through Reqistry, or report an app issue.
- Join the conversation on Product Hunt.
- Flutter stable with Dart. The checked-in lockfile requires Flutter ≥3.44.0 and Dart ≥3.12.0; dependency requirements are stricter than the package's declared Dart minimum.
- Android SDK, JDK 17, and an Android emulator or device.
- A matching Firebase configuration:
android/app/google-services.jsonis required by the Android Google Services Gradle plugin. Coordinate with the maintainer for the official project; for your own Firebase project, configure both that file andlib/firebase_options.dartconsistently.
git clone https://github.com/reqistry/reqistry-app.git
cd reqistry-app
flutter pub get
cp .env.example .env.prodEdit .env.prod before generating configuration:
| Variable | Local setup |
|---|---|
API_BASE_URL |
https://api.reqistry.dev |
PRIVACY_MD_URL |
https://api.reqistry.dev/static/privacy.md |
| App name, description, contact, and public links | Review the defaults in .env.example. |
ADMOB_ANDROID_APP_ID |
For local development, use Google's sample app ID: ca-app-pub-3940256099942544~3347511713. Debug/profile Dart code selects test ad units automatically. |
POSTHOG_PROJECT_TOKEN |
Set to an empty value to disable local telemetry, or use your own project's token. |
Both Dart environment generation and Android Gradle configuration read .env.prod. After editing it:
dart run build_runner build --delete-conflicting-outputs
flutter gen-l10n
flutter runEnvironment files and local signing files are gitignored. Generated lib/config/env.g.dart is currently tracked: review generated diffs and keep private credentials out of client configuration and commits.
flutter analyze
flutter test
flutter gen-l10n
flutter build apk --debugRelease signing reads key.properties at the repository root, pointing to a local keystore. Production releases also need the appropriate Firebase and AdMob configuration.
| Location | Responsibility |
|---|---|
lib/app/modules/views/ |
Screens and feature widgets |
lib/app/blocs/ |
Cubit state management |
lib/app/data/models/ |
API response models |
lib/app/services/ |
Networking, authentication, notifications, ads, and analytics |
lib/config/ |
Routes and environment configuration |
lib/l10n/ |
English and Spanish localization |
test/ |
Automated tests |
openapi.mobile.json |
Mobile API contract |
Read AGENTS.md for repository conventions before making changes.
| Problem | What to check |
|---|---|
| Dependency resolution fails | Run flutter --version and compare it with the SDK requirements above. |
Missing google-services.json / processDebugGoogleServices fails |
Add matching Firebase configuration to android/app/; the Gradle plugin requires it for debug builds too. |
Missing or stale env.g.dart values |
Fill in .env.prod, rerun dart run build_runner build --delete-conflicting-outputs, then rebuild the app. |
| Localization generation fails | Check the ARB syntax and matching keys in lib/l10n/app_en.arb and lib/l10n/app_es.arb, then run flutter gen-l10n. |
| Notifications do not arrive | Check Firebase configuration, device notification permission, and notification preferences. |
Missing release signing configuration |
Use a debug build for local development, or supply root-level key.properties and its referenced keystore for an authorized release. |
Still stuck? Open an issue with reproduction steps, expected and actual behavior, app/Android versions, and screenshots. For build problems, include flutter --version, the failing command, and relevant logs with credentials removed.
Bug reports, feature ideas, accessibility feedback, and localization improvements are welcome. Search existing issues first; discuss larger changes with the maintainer before implementation. For code contributions, review the licensing status below and run the quality checks above.
Built by Gwhyyy. Contact: work@gwhyyy.com. Privacy policy.
This repository does not currently include a LICENSE file. Public visibility alone does not grant an open-source license. Contact work@gwhyyy.com to clarify permission to use, modify, or redistribute the code.