Documentation

Commertize builds software that sponsors use to tokenize real estate, energy, credit and other real-world assets on transparent, auditable rails. Commertize is not a broker-dealer or exchange.

Commertize does not:

• Provide investment advice
• Act as a fiduciary
• Bypass securities, AML, or jurisdictional laws

These reads need no key and answer JSON. Limits are per client: news and listings 120 requests a minute, documentation 30.

• GET https://api.commertize.com/api/news: published Commertize news and commentary: headlines and summaries.
• GET https://api.commertize.com/api/news/{slug}: one article's full text, by slug.
• GET https://api.commertize.com/api/listings: the public listings feed: each publicly listed asset, its class, location and status. Informational only, not an offer.
• GET https://api.commertize.com/api/docs/content: this documentation as JSON sections (title, content, url).

Commertize's MCP server runs at agents.commertize.com/mcp and requires a bearer key in the Authorization header.

Each public read is limited per client IP in fixed one-minute windows: 120 requests a minute for news and listings, 30 for documentation. Over the limit the API answers HTTP 429 with a Retry-After header giving the wait in seconds.

On agents.commertize.com, a refused request comes back as JSON with an error code. A 401 also carries a message, for example {"error": "missing_credential", "message": "…"}. A 405 carries only error, plus allow on /mcp, for example {"error": "method_not_allowed", "allow": "POST"}. A 500 carries only {"error": "internal_error"}. An unknown path returns a plain-text 404 from the host, not JSON.

MCP protocol errors on agents.commertize.com (a request that cannot be parsed, a refused tool call) follow JSON-RPC 2.0: {"jsonrpc": "2.0", "id": …, "error": {"code": <integer>, "message": "…"}}, so there error is an object.

On api.commertize.com, errors come back as {"error": "<readable text>"}, for example {"error": "Unauthorized"} with HTTP 401. The text is for people and is not a stable code, and there is no message field.

• A request without a key is refused with HTTP 401 and "error": "missing_credential".

https://commertize.com/llms.txt lists these resources and the main Commertize pages in plain text.

Yes. The MCP server refuses requests without a bearer key.

An empty list means no published listing matches the query. Do not infer data from it.

Sponsors submit assets through structured intake workflows that capture:

• Asset type and jurisdiction
• Ownership and title
• Financial performance and projections
• Risk disclosures
• Intended investor audience

Note: AI systems assist with data validation and structuring recommendations but do not replace human or legal review.

Most assets are placed into bankruptcy-remote SPVs (LLCs, LPs, trusts, or equivalent). This ensures:

• Asset isolation
• Clear investor rights
• Enforceable security-to-asset linkage

Each digital security represents an interest in the SPV, not direct ownership of the physical asset.

Each digital security encodes:

• Ownership or economic rights
• Transfer restrictions
• Distribution entitlements
• Governance permissions (if applicable)

Smart contracts enforce:

• Who can hold the security
• Who can transfer the security
• When transfers are allowed
• How distributions are executed

After issuance, the issuer uses Commertize software for:

• Investor reporting
• Cash-flow distributions
• Ongoing compliance

Key risks include:

• Asset underperformance
• Digital securities are subject to the transfer restrictions in each offering's terms and applicable securities law, and there may be no market in which to sell them.
• Smart contract vulnerabilities
• Regulatory changes
• Market volatility

Investors bear asset-level risk. Commertize does not intervene in asset performance.