Bring Legal Payments
to Pydantic AI
Learn how to connect LawPay to Pydantic AI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the LawPay MCP Server?
Connect your LawPay account to any AI agent and manage legal payments through natural conversation.
What you can do
- Transaction Management — Browse payments, refunds, and charges with status tracking
- Invoice Tracking — List invoices with amounts, due dates, and payment status
- Trust Accounts — Monitor trust (IOLTA) account balances and transactions
- Payment Processing — Create charges and process payments
- Financial Reports — Access revenue summaries, payment trends, and aging reports
- Client Billing — Track client payment history and outstanding balances
How it works
1. Subscribe to this server
2. Enter your LawPay Secret Key and Merchant ID
3. Start managing payments from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Law Firms — manage client payments and trust accounts
- Legal Billing — track invoices and outstanding balances
- Finance Teams — access payment reports and reconciliation
Built-in capabilities (12)
Create a new invoice
Refund a transaction
Get account details
Get merchant profile info
Get payment statistics
Get payment method details
Get transaction details
). List merchant accounts
List payment invoices
List saved payment methods
List bank settlements
List all payment transactions
Why Pydantic AI?
Pydantic AI validates every LawPay tool response against typed schemas, catching data inconsistencies at build time. Connect 12 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your LawPay integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your LawPay connection logic from agent behavior for testable, maintainable code
LawPay in Pydantic AI
LawPay and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect LawPay to Pydantic AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for LawPay in Pydantic AI
The LawPay MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Pydantic AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
LawPay for Pydantic AI
Every tool call from Pydantic AI to the LawPay MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I manage trust account balances?
Yes. Monitor IOLTA trust account balances, view transactions per client matter, and track deposits and disbursements.
Does LawPay use Basic Auth?
Yes. LawPay uses HTTP Basic Auth with the Secret Key against api.affinipay.com/v1. The Merchant ID is required for identifying the account.
Can I track invoices and outstanding balances?
Yes. List all invoices with amounts, due dates, payment status, and client details. Monitor aging reports and outstanding balances.
How does Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your LawPay MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai