# FAQs #### General **Q: What is DeDi?** DeDi (Decentralized Directory) is an open protocol under Linux Foundation Decentralized Trust that defines a universal way to publish, discover, and verify public information. DeDi.global is a hosted implementation of this protocol, operated by Networks for Humanity Foundation. **Q: Is DeDi free?** Yes. DeDi.global is free to publish on and free to query. There are no licensing fees, contracts, or exit clauses. **Q: Is my data public?** Yes — DeDi is designed for public registries. Lookup and Query APIs are publicly accessible without authentication. If your data is sensitive or private, DeDi is not the right tool. **Q: How is DeDi different from a blockchain?** DeDi is not a blockchain. It is a directory protocol with a RESTful API. However, every entry's cryptographic proof is anchored on the CORD blockchain to provide tamper-evidence and auditability. You interact with DeDi via standard HTTPS APIs, not blockchain transactions. **Q: Can I run my own DeDi node?** DeDi is built on the open Decentralized Directory Protocol (DDP). Anyone can implement the protocol independently. DeDi.global is one implementation — not the only one. *** #### Account & Setup **Q: How do I create an account?** Register at [publish.dedi.global](https://publish.dedi.global/) with your email and a password (6+ characters with at least one special character). You'll receive a magic link to verify your email. **Q: How do I get an API key?** After registration and email verification, log in and use the "Get API Key" option in your profile, or call `GET /dedi/get-api-key` while authenticated. Include the key as a Bearer token in all API requests. *** #### Domain Verification **Q: Is domain verification mandatory?** No, but it is strongly recommended. Verification links your namespace to your domain, making API paths human-readable (e.g., `/dedi/your-domain.com/registry/record` instead of a hash) and establishing organizational provenance. **Q: How long does domain verification take?** The domain whitelisting request is typically processed within \~5 minutes. After adding the DNS TXT record, DNS propagation can take up to 24–48 hours depending on your DNS provider. **Q: Can I use DeDi without domain verification?** Yes. You can create namespaces, registries, and records without verification. Your namespace will use a system-generated ID instead of your domain name. *** #### Data & Schemas **Q: What credential formats does DeDi support?** DeDi is format-agnostic. It supports the co-existence of multiple data standards and schemas, including VC JSON-LD, mDocs/mDL, and custom JSON Schema (Draft 7). You define the schema when creating a registry. **Q: Can I define custom schemas?** Yes. You can provide any valid JSON Schema (Draft 7) when creating a registry. DeDi also offers pre-built schema templates (Membership, Public Key, Revocation, Beckn One). **Q: Can I bulk upload data via API?** Yes. DeDi provides a `POST /dedi/bulk-upload` endpoint that accepts CSV files via multipart/form-data. You can also bulk upload through the UI. See the [Bulk Upload guide](https://claude.ai/dedi.global-developers/guides/bulk-upload) for details. **Q: What happens if schemas don't match during upload?** The upload will fail. Schema consistency is required — your CSV column headers must match the registry's schema property names, and values must conform to the defined types. *** #### Verification & Trust **Q: How do I verify that a DeDi entry hasn't been tampered with?** Every DeDi entry includes a cryptographic proof (BLAKE2 H256 digest) anchored on the CORD blockchain. You can verify by recalculating the digest from the entry's fields and comparing it to the proof. You can also verify directly on-chain via [apps.cord.network](https://apps.cord.network/). **Q: Can I subscribe to changes in a registry?** Yes. The Watch feature lets you subscribe to changes on namespaces, registries, specific records, or schema tags. You receive notifications when entries are created, updated, or their state changes. *** #### Migration & Portability **Q: How do I migrate from another registry to DeDi?** Export your existing data as CSV, map your columns to a DeDi schema, and use the bulk upload feature. If you have a custom data format, define a matching JSON Schema when creating your registry. **Q: Can I export my data from DeDi?** Yes. Your data is exportable as standard JSON — fully portable. *** #### Support For additional questions, [contact support](https://docs.google.com/forms/d/e/1FAIpQLSesBZMkgmnKY3SDzGQPDF8E-OoAo75O5n4LVrdoDKFtz_Y3FA/viewform). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://dedi-global.gitbook.io/docs/miscellaneous/faqs.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.