Pela bronze

pela-site.pages.dev

“Pela's agent-facing translation surface. Two real endpoints: a bearer-key machine-translation REST API (POST /v2/translate, OpenAPI-described) and the PelaPela MCP server, which returns per-language-pair tuning guidance for another model's own translation output. Neither interface speaks the A2A protocol itself; each protocolBinding identifies the actual protocol the endpoint serves.

https://pela-site.pages.dev/.well-known/agent-card.json its card

Checked 2d ago extendedAgentCard, pushNotifications, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Let's Encrypt domain-validated
Valid until 5 Feb 2027 as of our check on 13 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA384, issued via YE2 under ISRG Root X2 — classical, as every publicly trusted certificate is today.

Names on this certificate (2)

*.pela-site.pages.dev, pela-site.pages.dev.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 13 Nov 2026. What this means
DANE / TLSA: Not verified
Discovery: Well-known document
AI use policy: Search: yesAI input: noAI training: no

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents: Publishes /llms.txt — “Pela” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 9 Oct 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: ? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked: 2d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of pela-site.pages.dev controls every word below.

Pela Translation API

Translate text with Pela's /v2/translate endpoint. Load when an agent needs machine translation into EN, ES, JA, ZH, KO, PT, FR, IT, or DE using a user-provisioned Pela API key.

translationlocalizationi18n

Examples it gives

Translate "Hello, how are you?" to Japanese

PelaPela translate tuning

Make your own translation output sound native using the PelaPela MCP server. Load before translating between English and Japanese or Spanish, or when translated text reads literal, mismatched in formality, or in the wrong script.

translationmcptonelocalization

Examples it gives

Tune an English-to-Japanese translation for a friendly tone in kana-only script

agenttru.st compared this card's skill list with every other listing's: 1 other listing declares an identical one, ignoring case, spacing and each card's own hostname. See all 2. That says the cards' text is the same, not who runs them.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: Pela — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 1.0.0
Auth schemes: bearerAuth
Card completeness: complete all eight fields required by a2a.proto v1.0

View all card details

Capabilities: extendedAgentCard pushNotifications streaming
Agent card: https://pela-site.pages.dev/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.