Pandektes puts legal-source access at the center of its €13.5m round

Pandektes plans to open more of its legal information through an API after announcing a €13.5 million Series A on October 5, 2026. For law firms and legal technology developers, the significance is access to a maintained collection of source documents that can feed their own applications. The funding announcement does not establish how complete that collection will be for any particular jurisdiction or task.

The company's October 5 announcement, also covered by The Next Web that day, names Alstin Capital as the lead investor, with PROfounders, Scale Capital and existing investors participating. Pandektes describes broader API access as part of its direction toward legal information infrastructure. That is the stated plan behind the financing; it is not a dated launch announcement for every advertised interface.

The API makes provenance a product requirement

Pandektes' current API page advertises its LegalQL query language across REST, MCP and CLI interfaces. The company describes filtering by court, legal state, relationships and time, with responses connected to their source. Access is offered by request. The page's illustrative response counts and timings are not independent performance evidence.

For a developer, those fields affect what an application needs to preserve. If a search filters documents by legal state and date, the surrounding product should carry that context through to the answer a user sees. Keeping a source link is useful, but dropping the version or the reason a document matched can make the result harder to check. This is an application-design implication, not a capability TechKili has tested.

Coverage has to match the legal question

The Legal Database description lists legislation, case law and administrative decisions, along with document history and connections down to individual paragraphs. It also advertises proprietary and unpublished decisions. These are the supplier's descriptions of its collection.

A buyer still needs a concrete account of coverage: which jurisdictions, courts, document types and periods are included, how quickly changes appear, and which gaps are known. A broad collection may help discovery while remaining insufficient for a specific research question. The financing itself does not answer those questions or independently validate the accuracy of generated legal analysis.

The distinction also matters when switching systems. A team should compare the sources needed for its actual work, including historical material, rather than infer equivalence from two platforms both offering AI-assisted search.

Follow one source through a pilot

A useful evaluation can start with a representative question for which the team already knows the authoritative documents. Retrieve those documents, inspect their dates and source connections, and follow them through the application's eventual answer. Include an amended document or a known coverage gap to see how the workflow handles uncertainty.

For an API integration, ask how updates, missing documents and changed identifiers are communicated. The reviewed public pages do not settle those contractual and operational details. They belong in the access discussion before a team depends on the service.

TechKili's assessment is that a traceable legal data layer could give builders more control over the evidence behind their tools. Its value in a particular deployment will depend on demonstrated coverage and a review process that checks whether cited material actually supports the answer.

Sources

• Pandektes: October 5 Series A announcement

• Pandektes: Platform API

• Pandektes: Legal Database

• The Next Web: October 5 funding report