slug: pydantic-ai
provider: PydanticAI
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 5
edges:
- tag: SCIM
  spec_file: pydantic-ai-scim-api-openapi.yml
  capability_id: BC-4230.50
  capability_id_l1: BC-4230
  capability_name: Tenant Identity Federation
  confidence: 0.8
  evidence: GET /scim/Users get_users_on_prem; PATCH /scim/{provider_name}/Groups/{group_id} update_group_cloud;
    schemas UserResourceRead, GroupResourceRead
  reason: SCIM user and group resources, including per-identity-provider paths, are exactly federated
    tenant identity and user/group lifecycle via SCIM for the SaaS tenant.
- tag: OAuth
  spec_file: pydantic-ai-oauth-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.75
  evidence: POST /oauth/register  Dynamic Client Registration (RFC 7591); 'you need to either create an
    OAuth App or a Personal Access Token'
  reason: The surface issues and revokes OAuth client registrations and tokens used by developers to call
    the public API — developer credential/OAuth client stewardship. Not a business-domain capability;
    it is the API ecosystem's credential management.
- tag: Organizations
  spec_file: pydantic-ai-organizations-api-openapi.yml
  capability_id: BC-4230.10
  capability_id_l1: BC-4230
  capability_name: Tenant Provisioning & Lifecycle
  confidence: 0.72
  evidence: POST /v1/organizations/  create_organization; POST /v1/organizations/{organization_id}/invitations/  Create
    Self Hosted Organization Invitation; schema SubscriptionPlanId
  reason: Create/update/delete of organizations plus invitations and a subscription plan id is creation
    and lifecycle of tenants in the multi-tenant Logfire service, i.e. tenant provisioning and lifecycle.
- tag: Alerts
  spec_file: pydantic-ai-alerts-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: POST /v1/projects/{project_id}/alerts/  Create Alert; schemas AlertChannelRead, Opsgenie,
    Webhook, AlertWithLastRun
  reason: Logfire is an observability product; alerts are rules evaluated over telemetry within a project,
    notifying via webhook/Opsgenie. This is observability/monitoring configuration, not financial or business
    alerting. Ambiguity only between Observability Management and Incident Response.
- tag: Dashboards
  spec_file: pydantic-ai-dashboards-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: POST /v1/projects/{project_id}/dashboards/  Create Dashboard; schemas DashboardPanel, DashboardQuery,
    DashboardDatasourceSpec
  reason: CRUD over dashboards of panels/queries against Logfire project telemetry — making the running
    service understandable in production. Could alternatively be read as general BI, hence 0.7.