_ registry / mcp http-sse · checked 1h ago

PersonAIzer.Sessions

https://www.personaizer.com

Registry code: cba926ae22eed018

api record
endpoint
https://sessions.personaizer.com/mcp
door code
9f34b79b770a2e23
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is PersonAIzer.Sessions live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is PersonAIzer.Sessions free to use?
Not measured yet.
What tools does PersonAIzer.Sessions have?
5 tools: chat, check_persona_status, upload_knowledge_docs, upload_knowledge_text, create_persona.
Is PersonAIzer.Sessions safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
182ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • chat unknown never probed

    Send a message to a PersonAIzer persona and get its reply, including any knowledge-base cards it surfaces. Requires your account API key and the persona_id to speak as.

    mcp-tool

    {
      "type": "object",
      "required": [
        "message",
        "personaId"
      ],
      "properties": {
        "message": {
          "type": "string",
          "description": "The message to send."
        },
        "personaId": {
          "type": "string",
          "description": "Which persona to chat with (its Persona ID)."
        },
        "sessionId": {
          "type": [
            "string",
            "null"
          ],
          "default": null,
          "description": "Continue an existing conversation by passing back the session_id from a previous chat call. Omit to start a new conversation."
        }
      }
    }
    arguments 25 lines
  • check_persona_status unknown never probed

    Poll the status of a persona build started by create_persona. Requires an account-level API key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "jobId"
      ],
      "properties": {
        "jobId": {
          "type": "string",
          "description": "The job_id returned by create_persona."
        }
      }
    }
    arguments 12 lines
  • upload_knowledge_docs unknown never probed

    Upsert up to 100 PRODUCTS (including services and unpriced catalog entries) into a knowledge source. For plain text (FAQs, policies, guides, articles, notes) use upload_knowledge_text instead. Requires your account API key; the source must exist (POST /v1/knowledge/sources).

    mcp-tool

    {
      "type": "object",
      "required": [
        "source",
        "items"
      ],
      "properties": {
        "items": {
          "type": "array",
          "description": "The products to upsert. Each needs title and categories (e.g. [[\"phones\"]]); id, description, price, in_stock, attributes, variants, images and links are optional — see PersonAIzer's /v1/knowledge API reference for the full shape."
        },
        "source": {
          "type": "string",
          "description": "The knowledge source the products belong to — its name, e.g. my-shop.ge."
        }
      }
    }
    arguments 17 lines
  • upload_knowledge_text unknown never probed

    Add a piece of text — an FAQ, policy, guide, article or notes — to a knowledge source as a plain-text document. Uploading again with the same id replaces that document's text. For products (price, stock, attributes, variants) use upload_knowledge_docs. Requires your account API key and the source to write to; every persona speaking for that source's brand answers from it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "content",
        "title",
        "source"
      ],
      "properties": {
        "id": {
          "type": [
            "string",
            "null"
          ],
          "default": null,
          "description": "Optional stable identifier. Uploading again with the same id replaces that document's text; omit it to create a new document."
        },
        "url": {
          "type": [
            "string",
            "null"
          ],
          "default": null,
          "description": "Optional URL where this content lives — shown as the document's link when the persona cites it."
        },
        "title": {
          "type": "string",
          "description": "Document title."
        },
        "source": {
          "type": "string",
          "description": "The knowledge source this belongs to — its name, e.g. my-shop.ge."
        },
        "content": {
          "type": "string",
          "description": "The full text of the document."
        }
      }
    }
    arguments 38 lines
  • create_persona unknown never probed

    Start building a new PersonAIzer persona from a website URL — reads the site's brand facts, makes the brand, synthesizes the persona's identity and avatar, and (by default) crawls the site into the brand's knowledge; the persona and the crawl run in parallel. Asynchronous (~1 minute for the persona) — returns jobId, brandId and personaId; poll check_persona_status. Requires an account-level API key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "websiteUrl"
      ],
      "properties": {
        "websiteUrl": {
          "type": "string",
          "description": "The website URL to build the persona from."
        },
        "harvestContent": {
          "type": "boolean",
          "default": true,
          "description": "Whether to crawl the site into the brand's knowledge alongside the persona build (default true)."
        }
      }
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cba926ae22eed018.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cba926ae22eed018/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cba926ae22eed018/badge.svg)](https://brick.blue/agent/cba926ae22eed018?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.