Firstbase vs Beglaubigt.de

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Beglaubigt.de
   Firstbase—none0/10

   Firstbase is a business-formation/back-office SaaS, and while agent-oriented docs are a fair axis for any modern SaaS, a direct probe shows llms.txt returns 404 and no other agent-oriented documentation format is evidenced.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”

   proof ↗⚑ flag

   Beglaubigt.de✓fullprobed8/10

   Beglaubigt.de has a live llms.txt confirmed via direct probe (HTTP 200) plus an llms-full.txt with detailed API/event docs, and a separate marketing-domain llms.txt listing product capabilities, giving agents a clear entry point into agent-oriented documentation. Missing for 10: no OpenAPI/machine-readable schema (probe shows 404s) and no independent third-party confirmation of agent usage.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”
   • [claimed-docs] “Digital notarization of legal documents (under 48h)”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

2. ai-native userDrive the product through a documented public API

   weight 3 · round to Beglaubigt.de
   Firstbase—none0/10

   No evidence of a documented public API; probes for llms.txt and OpenAPI/Swagger specs all returned 404, and no docs mention API access for AI-native or programmatic use.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de✓fullprobed8/10

   Beglaubigt.de publishes a documented public API with clear endpoints for incorporation, notarization, translation, tax and trade registration, webhooks, and signature verification, confirmed live via llms.txt probe (HTTP 200). Missing for 10: a discoverable OpenAPI/Swagger spec (all standard paths 404) and independent third-party corroboration of API usage.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

3. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Firstbase—none0/10

   Firstbase is a business incorporation/back-office service with no evidence of any SDK offering; probes for llms.txt and OpenAPI specs both returned 404s, and no docs mention SDKs at all.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Evidence shows a REST API with docs and webhooks, but there is no mention of official SDKs, client libraries, or language-specific packages, and the OpenAPI spec probe returned 404s across all candidate paths, suggesting no machine-consumable spec to auto-generate SDKs either.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”

   proof ↗⚑ flag

4. ai-native userSubscribe to events via webhooks

   weight 2 · round to Beglaubigt.de
   Firstbase—none0/10

   No evidence of any webhook subscription capability, API, or event system in Firstbase's documentation; probes for OpenAPI/llms.txt both returned 404, and no docs mention webhooks at all.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed6/10

   Docs describe webhook events (e.g., appointment.completed), real-time notarization notifications, and HMAC-SHA256 signature verification for incoming webhook payloads, indicating an event-driven webhook system exists. However, there's no explicit documentation of a subscription/registration endpoint or full event catalog for AI-native automation. Missing for 10: explicit webhook subscription/management API, full list of subscribable event types, and independent confirmation of webhook reliability.

   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Firstbase—none0/10

   No evidence of AI-generated insights, analytics, or suggestions within Firstbase's product; the pack only describes compliance, banking, mail, and accounting services delivered by humans or manual processes.

   ⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de is a notarization/incorporation workflow API; the only AI-related mention is signature/date field auto-detection during document processing (beglaubigt-docs-5), which is a document-parsing feature, not AI-generated insights or suggestions surfaced to the user from their data. No evidence of dashboards, analytics, recommendations, or generative insights derived from user data.

   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Beglaubigt.de
   Firstbase—none0/10

   Firstbase is a company-formation/back-office service; nothing in the evidence describes AI-agent automation building, scheduling, or autonomous background workflows for users. No API, no llms.txt, no automation builder is documented — probes for openapi/llms.txt both 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed5/10

   The API supports triggering document workflows (incorporation, notarization, translation, tax registration) and emits webhook events like appointment.completed with HMAC-signed real-time notifications, which together allow building background automations that react to business events without manual polling — docs explicitly claim businesses can 'automate notarization workflows'. However there is no evidence of a built-in scheduler, multi-step workflow builder, or agent-triggered chaining beyond basic API+webhook usage. Missing for 10: evidence of a no-code/automation builder, orchestration across multiple document types, third-party automation platform integrations, and independent confirmation that webhooks reliably drive autonomous flows.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Firstbase—none0/10

   No evidence of any natural-language command interface, chat-based control, or AI-native operation; probes for llms.txt and OpenAPI both failed, and all docs describe a traditional web-form/dashboard business-services product.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Evidence shows only structured REST API endpoints (incorporation, notarization, translation, tax registration) and llms.txt files aimed at helping AI agents read documentation — there is no chat interface, NL command parser, or agentic control surface letting an end user type natural-language instructions to operate the product.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Firstbase—none0/10

   Firstbase is a business-formation/back-office platform; no evidence of any API reference, interactive docs, or runnable examples—probes for llms.txt and OpenAPI specs both returned 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   The docs describe endpoints (POST/GET) for incorporation, notarization, translation, etc., but there is no evidence of an interactive API reference with runnable examples (e.g., embedded try-it console, SDK code snippets executable in-browser). A probe explicitly found no OpenAPI/Swagger spec at common paths, undermining any interactive reference tooling. Missing for 10: interactive 'try it' console, runnable code samples, OpenAPI/Swagger spec availability.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Firstbase—none0/10

   Probes explicitly show no OpenAPI/swagger spec exists at any expected location, and no docs mention a public API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   A direct probe for OpenAPI/Swagger spec files at common paths returned 404 on all candidates, and no evidence pack item references a downloadable machine-readable API spec — only an llms.txt (plain text docs index) exists, which is not an OpenAPI-equivalent schema.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Firstbase—none0/10

   No evidence of any public API, versioning scheme, or deprecation policy; probes for llms.txt and OpenAPI specs both returned 404, and Firstbase's docs focus entirely on incorporation/compliance services, not developer APIs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   The API endpoints use a /v1/ prefix suggesting some versioning, but there is no documented deprecation policy, versioning strategy, or changelog anywhere in the evidence; OpenAPI spec probes even returned 404s. missing for 10: documented versioning scheme, deprecation policy, changelog, migration guidance.

   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Firstbase—none0/10

   No evidence of any bulk/batch operations capability across items; Firstbase is a company formation/back-office service with no API or bulk automation features documented, and probes confirm no API/llms.txt exists.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   The API supports creating individual notarization, translation, incorporation, and tax-registration requests, and translation requests can include 'one or multiple documents,' but there is no evidence of batch/bulk endpoints, list-based submission across many items, or bulk status operations. No documentation of pagination-based bulk retrieval, batch job submission, or CSV/array-based multi-record processing was found.

   • [claimed-docs] “This endpoint creates a translation request for one or multiple documents.”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”

   proof ↗⚑ flag

Compliance

1. founderFile annual reports and franchise tax on time through the platform

   weight 2 · round to Firstbase
   Firstbase~partialcommunity6/10

   Firstbase documents a compliance dashboard showing per-state deadlines and required actions, registered agent service, and tax filing (extension filing, R&D eligibility) — covering the general mechanics of annual report/franchise tax compliance. However, evidence doesn't explicitly confirm automated annual report filing itself (vs. just deadline tracking), and a community report confirms users still must independently handle annual state filings/fees themselves. Missing for 10: explicit confirmation that Firstbase files annual reports/franchise tax on the founder's behalf (not just tracks deadlines), and independent verification of on-time filing success.

   • [claimed-docs] “Get an instant overview of your company’s status in each state. Click on a state to view requirements, upcoming deadlines, and take any nece…”
   • [claimed-docs] “Need to expand your business to a new state? No problem. Just select a state on your compliance dashboard and we’ll take care of it for you.”
   • [claimed-docs] “Register for Payroll™ to compliantly hire remote employees, process payroll, and file tax returns. Available in all 50 states.”
   • [claimed-docs] “Subscribe by April 15 and we'll file an extension form ASAP”
   • [community] “Used Firstbase, it's cheaper and took me 2 weeks to get up and running. From Uganda. Firstbase supports Stripe, sets up US bank account with…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Evidence shows only one-time post-incorporation filings (tax registration via ELSTER, trade registration, transparency register entry) at company formation, not recurring annual report or franchise-tax filing services on an ongoing basis. Missing for 10: any evidence of recurring/annual compliance filing, franchise tax handling, or ongoing registered-agent style maintenance work.

   • [claimed-docs] “Submit a company's details to start its tax registration. An ELSTER XML document will be generated and sent the tax office”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “Wir übernehmen die Pflichtmeldungen nach Gründung: Transparenzregister-Eintrag, Gewerbeanmeldung und Anmeldung beim Finanzamt.”

   proof ↗⚑ flag

2. legal-ops leadSee a compliance calendar of upcoming filing deadlines and get reminders before each one

   weight 2 · round to Firstbase
   Firstbase~partialclaimed5/10

   Firstbase's registered-agent/compliance dashboard gives an overview of state-by-state status and upcoming deadlines (firstbase-docs-7, firstbase-docs-14), which is the closest match to a compliance calendar, but there's no evidence of proactive reminder/notification mechanisms (email/SMS alerts) before deadlines. missing for 10: explicit reminder/notification feature description, evidence of calendar/alert scheduling, independent confirmation the dashboard surfaces deadlines accurately.

   • [claimed-docs] “Get an instant overview of your company’s status in each state. Click on a state to view requirements, upcoming deadlines, and take any nece…”
   • [claimed-docs] “Need to expand your business to a new state? No problem. Just select a state on your compliance dashboard and we’ll take care of it for you.”
   • [claimed-docs] “Your bookkeeper is always available to answer any questions about accounting dates, deadlines, regulations.”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de offers notarization, incorporation, and registration APIs with event webhooks, but there is no evidence of a compliance calendar view or proactive deadline reminders for legal-ops tracking of filing deadlines. Event webhooks like appointment.completed are transactional notifications, not a forward-looking deadline calendar.

   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”

   proof ↗⚑ flag

Compliance agentic

1. ai-native userDelegate an annual report or compliance filing to an agent that prepares it through the platform with minimal human input

   weight 2 · round to Beglaubigt.de
   Firstbase—none0/10

   Firstbase offers a human-facing registered-agent and compliance dashboard, but there is no evidence of any AI-agent API, automation hooks, or delegation workflow that would let an AI agent prepare filings with minimal human input; probes even confirm no llms.txt or OpenAPI endpoint exists for programmatic/agentic access.

   • [claimed-docs] “Get an instant overview of your company’s status in each state. Click on a state to view requirements, upcoming deadlines, and take any nece…”
   • [claimed-docs] “Need to expand your business to a new state? No problem. Just select a state on your compliance dashboard and we’ll take care of it for you.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed5/10

   Beglaubigt.de exposes APIs for tax-registration, trade-registration, incorporation and notarization with webhooks (e.g. appointment.completed) that could plausibly be orchestrated by an agent with minimal human input, but there is no evidence of an 'annual report' filing endpoint or of any product feature specifically marketed as agent-delegated compliance preparation. missing for 10: explicit annual report/Jahresabschluss filing capability, evidence of an actual autonomous agent workflow completing filings end-to-end, and confirmation that human signatures/appointments aren't still required as bottlenecks.

   • [claimed-docs] “Submit a company's details to start its tax registration. An ELSTER XML document will be generated and sent the tax office”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [claimed-docs] “Wir übernehmen die Pflichtmeldungen nach Gründung: Transparenzregister-Eintrag, Gewerbeanmeldung und Anmeldung beim Finanzamt.”

   proof ↗⚑ flag

Doc api

1. developerGenerate, populate, and send legal documents programmatically through a documented API

   weight 3 · round to Beglaubigt.de
   Firstbase—none0/10

   No evidence of a documented API for generating, populating, or sending legal documents; probes for OpenAPI/llms.txt endpoints returned 404s, and all docs describe manual/back-office services, not developer APIs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de✓fullprobed7/10

   Documentation shows concrete POST endpoints for creating incorporation, notarization, translation, tax-registration, and trade-registration requests, plus GET endpoints and webhook events, indicating a genuine programmatic API for populating/sending legal documents. However, missing for 10: a discoverable OpenAPI/Swagger spec (probe found all candidate spec URLs 404), independent developer corroboration or third-party usage reports, and detail on request/response schemas or SDKs.

   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint retrieves the details of an incorporation”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “This endpoint creates a translation request for one or multiple documents.”
   • [claimed-docs] “Submit a company's details to start its tax registration. An ELSTER XML document will be generated and sent the tax office”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

Hiring

1. legal-ops leadRun hiring and equity paperwork — offer letters, confidentiality/IP agreements, and option grants — through the platform

   weight 2 · round drawn
   Firstbase—none0/10

   Evidence covers incorporation, registered agent, banking, payroll registration, accounting, and tax filing, but nothing about offer letters, confidentiality/IP agreements, or option/equity grant paperwork for hiring.

   ⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de's documented capabilities cover generic document notarization, translation, incorporation, tax/trade registration, and apostilles for German companies — but no evidence pack item mentions offer letters, confidentiality/IP agreements, or option grants, nor any equity/HR paperwork workflow support. The evidence shows only signature-field detection on arbitrary uploaded documents, which is not the same as a legal-ops equity/hiring document suite.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”

   proof ↗⚑ flag

Esign

1. founderSend a document for legally binding e-signature to multiple recipients with routing

   weight 3 · round to Beglaubigt.de
   Firstbase—none0/10

   No evidence in the pack mentions e-signature functionality, document routing, or multi-recipient signing workflows; Firstbase's evidence covers incorporation, compliance, banking, accounting, and mail services only.

   ⚑ flag

   Beglaubigt.de~partialclaimed3/10

   Beglaubigt.de's docs mention submitting documents and managing signers for notarization requests with AI-detected signature fields, which implies some multi-signer capability, but there is no evidence of routing logic (sequential/parallel order, per-recipient roles) for standard e-signature workflows — the platform's core focus is notarization/incorporation, not generic e-signature routing. Missing for 10: explicit routing/order configuration for multiple recipients, confirmation that signatures are 'legally binding e-signatures' rather than tied only to notarization appointments, and any independent corroboration of multi-recipient workflows.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Beglaubigt.de
   Firstbase—none0/10

   No evidence of any public API at all — probes for llms.txt and OpenAPI/Swagger endpoints returned 404, and no docs mention an API for parity with UI features.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de~partialprobed6/10

   The docs show a genuine API-first design covering the core workflows also available in the UI—incorporation, notarization, translation, tax registration, and trade registration (docs-2,4,6,7,8), plus webhooks/signature verification for automation (docs-9,10,11), and the company explicitly markets itself as the first in Germany to offer incorporation via API (docs-22). However, some UI-surfaced conveniences (free business account bundling, company-name availability check, package selection in docs-17/18) aren't confirmed as API endpoints, and no discoverable OpenAPI/swagger spec was found (probe-2 all 404), making full UI/API parity unverifiable. Missing for 10: confirmed API endpoints for all UI-only conveniences (name check, account bundling), and a published machine-readable OpenAPI spec.

   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “This endpoint creates a translation request for one or multiple documents.”
   • [claimed-docs] “Submit a company's details to start its tax registration. An ELSTER XML document will be generated and sent the tax office”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “beglaubigt.de bietet als erstes Unternehmen in Deutschland eine API-Schnittstelle zur UG / GmbH Gründung in Zusammenarbeit mit Notaren.”
   • [claimed-docs] “Prüfe, ob dein Wunschname verfügbar ist – und gründe in wenigen Minuten”
   • [claimed-docs] “Erhalte ein kostenloses Geschäftskonto zu jeder Unternehmensgründung”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Firstbase—none0/10

   No evidence of any data export functionality in open formats; Firstbase is a business incorporation/back-office service with no documented export/portability feature, and probes for llms.txt and OpenAPI both 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de is a notarization/incorporation API service, not a data-storage platform, but the story asks whether users can export their own data (documents, records) in open formats and leave — no evidence of any export/download-all-data feature or data portability mechanism appears anywhere in the docs. This is a fair question since users submit sensitive documents and company data that they'd reasonably want to retrieve or migrate away with, so the axis applies, and no evidence of such a capability exists.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “This endpoint creates a translation request for one or multiple documents.”

   proof ↗⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Firstbase—none0/10

   Firstbase is a company-formation/back-office platform; none of the evidence addresses AI data retention, data deletion controls, or privacy settings for AI-native use of user data. Absence of any mention of data retention/deletion policy means this applicable axis is unmet.

   ⚑ flag

   Beglaubigt.de—none0/10

   No evidence of any data retention controls, deletion endpoints, or privacy/data lifecycle settings in the docs; the evidence pack covers notarization, incorporation, translation, and webhook features only.

   ⚑ flag

Templates

1. founderAnswer guided questionnaires that fill in legal documents correctly and flag choices that need attorney review

   weight 1 · round to Beglaubigt.de
   Firstbase—none0/10

   Evidence shows Firstbase handles incorporation, registered agent, banking, accounting, and payroll services, but there is no mention of guided questionnaires that fill in legal documents or flag choices needing attorney review — missing for 10: any documented questionnaire/document-assembly workflow, any attorney-review flagging feature, any templates library.

   ⚑ flag

   Beglaubigt.de~partialclaimed3/10

   There is evidence of structured data submission for incorporation (company details, shareholders, directors) and a digital tax registration questionnaire submitted via ELSTER, which resembles guided form-filling, but nothing describes a questionnaire flow that validates legal choices or flags items requiring attorney review — the process instead routes to real notaries for the legal check, not an in-app flagging mechanism. Missing for 10: evidence of a structured Q&A/questionnaire UI, logic that flags legally risky choices, and any attorney-review escalation feature.

   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “Der Fragebogen zur steuerlichen Erfassung wird vollständig digital ausgefüllt und über die offizielle ELSTER-Schnittstelle an das Finanzamt …”
   • [claimed-docs] “Company incorporation (UG, GmbH, Holding structures)”

   proof ↗⚑ flag