Getting Started

Welcome to DPO2U's technical documentation. This guide walks you through the first steps of interacting with the protocol, whether you are a company seeking to emit compliance proofs, or a developer integrating AI Agents.

Prerequisites

Before you begin, ensure you have:

• A DPO2U MCP Server URL (or the ability to run it locally)
• Basic familiarity with blockchain concepts and API integrations
• curl or any HTTP client for testing tool calls

For companies

If you are a business operating with user data, participating in DPO2U enables you to mathematically prove your compliance without ever leaking the sensitive data you manage.

1. Request an LGPD Kit

Contact the DPO2U team or use the MCP Server's generate_lgpd_kit tool to produce a complete privacy policy package. The tool analyzes your company profile and data processing activities and generates a policy.json strictly governed by the dpo2u/lgpd/v1 schema.

2. Review and approve

The generated kit includes privacy policies, data processing records, and a DPIA (Data Protection Impact Assessment). Your legal team reviews the documents before submission.

3. Produce the attestation result

Once approved, the DPO2U workflow can encrypt and store the relevant artifacts off-public-surface, preserve stable references for evidence, and produce an attestation-oriented result for validation and review.

4. Monitor compliance

Use the live MCP runtime to verify the currently exposed compliance-related capabilities and retrieve status or validation outputs through the currently documented tool surface. Do not assume that every verification backend is publicly reachable in the same way.

For developers & AI agents

If you are a developer looking to integrate DPO2U into your AI pipelines, the primary entry point is the MCP Server. All interactions use standard HTTP requests — no proprietary SDK required.

Checking compliance status

curl

curl -X POST https://mcp.dpo2u.com/tools/check_compliance_status \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $DPO2U_API_KEY" \
  -d '{
    "company_id": "hashed-cnpj-identifier"
  }'

Response shape varies by the live runtime surface.

{
  "status": "ok",
  "result": {
    "compliance_state": "available-via-runtime",
    "evidence_reference": "cid-or-id-if-applicable",
    "validated_at": "runtime-dependent"
  }
}

TypeScript

const response = await fetch('https://mcp.dpo2u.com/tools/check_compliance_status', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': `Bearer ${process.env.DPO2U_API_KEY}`,
  },
  body: JSON.stringify({
    company_id: 'hashed-cnpj-identifier',
  }),
});

const result = await response.json();

if (!result.compliant) {
  console.log('Supplier is not compliant. Aborting data transfer.');
  process.exit(1);
}

console.log(`Compliance score: ${result.score}/100`);

Workflow

Using the MCP Server gives your LLMs and applications a standard way to interact with DPO2U capabilities. For the exact currently exposed operations, inspect the live MCP runtime and its OpenAPI description rather than assuming a static tool list or a fixed public settlement path.

MCP Server

For detailed API usage, authentication, error handling, and the full list of exposed tools, head to the MCP Server documentation.

What's next

• MCP Server — full API reference, authentication, and error codes
• Architecture — understand the runtime surfaces and trust boundaries
• Schemas — the dpo2u/lgpd/v1 schema specification