policyengine-api-v2

Name: policyengine-api-v2
Availability: InStock
Author: PolicyEngine

Present a monorepo blueprint for PolicyEngine v2 microservices with uv tooling.

2|Updated Mar 31, 2026

Search Tags:#api #openapi #microservices #uv #supabase #docker #monorepo

Ready to run

npx skills add https://github.com/PolicyEngine/policyengine-skills --skill policyengine-api-v2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: policyengine-api-v2
Source: https://github.com/PolicyEngine/policyengine-skills/tree/main/skills/tools-and-apis/policyengine-api-v2-skill
Command: npx skills add https://github.com/PolicyEngine/policyengine-skills --skill policyengine-api-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, ready-to-use blueprint for building and deploying PolicyEngine API v2 microservices in a monorepo, reducing setup friction and accelerating onboarding for engineers and analysts.

Core Features & Use Cases

Monorepo layout with api-full, api-simulation, and api-tagger services, plus a shared utilities folder.
OpenAPI spec generation and client tooling to streamline integration.
uv-based dependency management and Docker-based local development.
Supabase-backed PostgreSQL for persistent data and authentication.
Clear migration path from v1 and roadmap visibility for contributors.

Quick Start

Clone this repository and review the api-full, api-simulation, and api-tagger folders to understand the v2 architecture.

Frequently Asked Questions about policyengine-api-v2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure a microservices monorepo for API development?▼

A microservices monorepo for API development separates logic into distinct service folders like api-full, api-simulation, and api-tagger, alongside shared utilities. This layout streamlines dependency management, OpenAPI generation, and Docker-based local development across multiple services.

What is the best way to manage Python dependencies in a microservices monorepo?▼

Managing Python dependencies in a microservices monorepo is optimized using uv-based tooling. This approach provides fast, reliable package management across shared utilities and individual services, ensuring consistent local development and deployment environments.

How do I generate OpenAPI specs for multiple microservices?▼

Generating OpenAPI specs for multiple microservices involves using built-in client tooling within the monorepo blueprint. This streamlines API integration by automatically producing documentation and client libraries from the api-full, api-simulation, and api-tagger services.

Can I use Supabase as a PostgreSQL backend for microservices?▼

Yes, Supabase can be used as a PostgreSQL backend for microservices. It provides persistent data storage and built-in authentication, integrating seamlessly with a Docker-based local development setup to support scalable API architectures.

Does this monorepo blueprint include a migration path from v1?▼

Yes, the monorepo blueprint includes a clear migration path from v1 architecture. It provides roadmap visibility for contributors, ensuring a structured transition when moving existing APIs to the new api-full, api-simulation, and api-tagger service structure.