Skip to content
Get 25 free leads

Draft — pending legal review · This document hasn't been approved by counsel yet and may change.

End User License Agreement

Effective

This End User License Agreement ("EULA") is between J&T Solutions Inc., a Delaware corporation doing business as Diced, 251 Little Falls Drive, Wilmington, DE 19808, United States ("Diced", "we", "us"), and the customer that uses the Diced software ("you").

This EULA is part of the Terms of Service. Words defined in the Terms have the same meaning here. If this EULA and the Terms conflict, the Terms control.

Questions go to legal@diced.si. Technical help is at support@diced.si.

1. What this EULA covers

The "Software" means:

  • the web app at app.diced.si;
  • the REST API at api.diced.si/v1 and its OpenAPI specification;
  • the MCP server at api.diced.si/mcp, and its OAuth sign-in for connectors;
  • webhooks the Services send to you;
  • the Documentation at docs.diced.si, including code samples;
  • any updates to these.

Diced provides the Software as a hosted service. We do not ship downloadable software.

2. License

While your account is active and you comply with the Terms, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use the Software for your internal business purposes, under the Documentation, the Terms and the Acceptable Use Policy.

Code samples. You may copy and change the code samples in the Documentation, such as the curl, JavaScript and Python examples and the webhook signature verification code, and use them in your own software to work with the Services.

We reserve all rights not expressly granted.

3. API keys

API keys start with dcd_live_. A workspace owner or member who has accepted the Acceptable Use Policy creates them in Developers. We show each key once and store only a hash of it.

  • Treat keys like passwords. Do not put them in client-side code, public repositories or shared documents.
  • You are responsible for every request made with your keys.
  • Revoke a key at once if you think it has leaked. Tell us at support@diced.si if someone misused it.
  • A key works only for the workspace it belongs to. Do not share keys with anyone outside your organization.

4. Usage limits

The current limits are in the Documentation. At launch they are:

  • 120 API requests per minute per key. Responses include RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers. Over the limit, we return HTTP 429 with a Retry-After header.
  • 30 "describe" requests per minute per workspace.
  • Up to 10,000 rows per enrichment batch.
  • Up to 100 items per page on list endpoints.
  • Idempotency-Key values on chip-spending requests are honored for 24 hours.

We may change limits to protect the Services. We will give notice in the Documentation or by email before lowering a limit that affects normal use, unless we need to act right away to stop abuse or an outage. Sign-in, the public demo and privacy requests have their own limits.

You may not get around limits, for example by creating extra workspaces or keys or spreading requests across accounts.

5. Spending chips through the Software

Requests that reveal leads, enrich data or auto-reveal watched audiences spend chips as the Terms describe. Chip-spending API and MCP requests take a maximum, such as max_chips, and we will not charge more than it. Chip-spending MCP tools are marked as not read-only so that the client can ask you before running them.

You are responsible for chips spent by your code, your integrations and any AI agent you connect. Set caps you are comfortable with. Chips spent this way are not refundable, as the Terms explain.

6. MCP server and AI connectors

You can connect AI assistants and tools, such as Claude, ChatGPT and Cursor, to the MCP server with an API key or through OAuth sign-in. When you approve a connection, you choose a workspace, and the connector acts for that workspace.

  • The connector, and the company that runs it, is a third party. Its terms and privacy policy apply to what you send it and what it does with Lead Data it receives. We are not responsible for it.
  • Lead Data that an AI assistant retrieves stays subject to the Terms and the Acceptable Use Policy. Do not let a connector reuse, publish or train on Lead Data. [CONFIRM: whether to require customers to turn off training or data retention in AI tools that receive Lead Data, and how that fits the data partner agreement.]
  • You can disconnect a connector at any time under Developers, MCP. Disconnecting ends its access.

7. Webhooks

Webhook endpoints must use HTTPS and must be systems you control or are authorized to use. Each endpoint has its own signing secret. Verify the Diced-Signature header before you trust a payload.

We retry failed deliveries for about 24 hours. After three events in a row fail every retry, we disable the endpoint and email the workspace owners. Webhook payloads can contain full Lead Data, so protect the systems that receive them.

8. Restrictions

You may not, and may not let anyone else:

  • copy, modify, translate or create derivative works of the Software, except code samples under section 2;
  • reverse engineer, decompile or disassemble the Software, or try to discover its source code, data sources, or how it gets its data, except where the law allows despite this restriction;
  • scrape, crawl or harvest the Services, or access them through automated means other than the API and MCP server as documented;
  • run requests designed to rebuild, copy or map our dataset, for example by enumerating filters or topics to collect masked previews;
  • probe, scan or test the vulnerability of the Services, or break or get around authentication, rate limits, chip caps or masking. Security research is welcome if you report it to legal@diced.si first and follow our instructions;
  • interfere with or overload the Services, or send malicious code;
  • use the Software to build or train a competing product or dataset;
  • resell, rent, sublicense or offer the Software to third parties as a service bureau, unless we agree in writing;
  • remove or hide any notices of ownership.

9. Changes, versions and deprecation

The API is versioned in its path, starting with /v1. We may add endpoints, fields, events and filter values to a version without notice. Build your code to ignore fields it does not know.

We will give at least 90 days' notice by email or in the Documentation changelog before we remove or make a breaking change to a stable /v1 endpoint or MCP tool, unless we need to act sooner for security, legal or data partner reasons. [CONFIRM: 90-day deprecation notice period.]

Features marked beta or preview may change or end at any time. They are provided as is, and our total liability for them is US$100.

10. Third-party components

The Software uses open-source components. Their licenses apply to those components.

11. Disclaimer and liability

The disclaimers, limitation of liability and indemnity sections of the Terms apply to the Software. THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE". We do not warrant that it will be uninterrupted, error-free or compatible with any client, connector or AI model.

12. Termination

This license ends when your account ends, when the Terms end, or when we end it for a breach. We may revoke API keys or disconnect MCP clients that break this EULA or put the Services at risk. When the license ends, stop using the Software and delete your API keys.

13. U.S. government use

The Software is commercial computer software and documentation. U.S. government users get only the rights in this EULA, as provided in FAR 12.212 and DFARS 227.7202.

14. Disputes

Disputes about this EULA are resolved under section 14 of the Terms, including Delaware governing law, AAA arbitration in Wilmington, Delaware, and the class action and jury waivers.

15. Contact

J&T Solutions Inc., doing business as Diced 251 Little Falls Drive, Wilmington, DE 19808, United States