# Build a tenant-safe company lookup service

Use case · Platforms · Planned API workflow

Canonical page: https://datasdk.ai/use-cases/build-a-tenant-safe-company-lookup-service

Plan company lookup around authorized customer contexts.

## Who this helps

A multi-customer platform needs stronger boundaries than a shared list of companies.

## How to use it

1. Define which customer and website own each request.
2. Enforce access checks on the server and keep results scoped.
3. Confirm the API contract and test cross-tenant failure cases.

## Illustrative example

A proposed backend would reject a lookup request for a website outside the customer's workspace.

## What to check

This is an integration design; API access and permitted use must be confirmed.

## How Data SDK fits

The full Data SDK API is coming soon. Platform and AI-agent workflows are planning examples. Confirm access, data delivery, usage, branding, and resale terms before building or selling a feature.

These are suggested workflows, not a list of built-in integrations. Use your own approved analytics, CRM, and research process where needed. Matches and fields vary. A company match does not identify a person or prove buying intent.

## Related reading

- [Server-side request](https://datasdk.ai/glossary/server-side-request): A server-side request is sent by backend software rather than directly by a visitor's browser.
- [Tenant isolation](https://datasdk.ai/glossary/tenant-isolation): Tenant isolation keeps one customer's data and actions separate from another's.
- [Least privilege](https://datasdk.ai/glossary/least-privilege): Least privilege gives software only the access needed for its task.
- [Offer identification in a website-builder product](https://datasdk.ai/use-cases/offer-identification-in-a-website-builder-product): Plan identification as a clearly explained optional website capability.
- [Design a graceful no-match experience](https://datasdk.ai/use-cases/design-a-graceful-no-match-experience): Avoid misleading users with guessed names or stale company cards.
- [Plan a retry-safe enrichment workflow](https://datasdk.ai/use-cases/plan-a-retry-safe-enrichment-workflow): Design safer retries before connecting company data to actions.

[Glossary](https://datasdk.ai/glossary) · [Use cases](https://datasdk.ai/use-cases) · [Comparisons](https://datasdk.ai/vs) · [For businesses](https://datasdk.ai/for-businesses) · [For builders](https://datasdk.ai/for-builders)