Sitecore CDP Server

Created By
markstilesa year ago
Overview

what is Sitecore CDP Server?

Sitecore CDP Server is a server application designed to interact with the Sitecore Customer Data Platform (CDP) using the Guest REST API. It is built with TypeScript and Express, providing a structured way to manage guest data.

how to use Sitecore CDP Server?

To use Sitecore CDP Server, clone the repository, install the dependencies, and configure your environment variables. You can then build the project and run the server manually if needed.

key features of Sitecore CDP Server?

  • Interacts with Sitecore CDP using Guest REST API
  • Built with TypeScript and Express for robust server management
  • Easy configuration through environment variables

use cases of Sitecore CDP Server?

  1. Managing guest data for personalized marketing campaigns.
  2. Integrating customer data from various sources into Sitecore.
  3. Automating data retrieval and updates in the Sitecore CDP.

FAQ from Sitecore CDP Server?

  • What programming language is used for Sitecore CDP Server?

Sitecore CDP Server is built using TypeScript.

  • How do I configure the server?

You need to create a .env file with your API keys and other necessary configurations based on the provided example.

  • Can I run the server manually?

Yes, you can run the server manually after building the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
markstiles
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago