Pelican Score.Take the test ↗
← Score another pelicanPELICAN-V1 / AD6151F0
Check the rendered imageUnsupported or unsafe SVG content was removed. The judge scores this PNG; compare it with your original before interpreting the score.
Your sanitized SVG, rendered as a PNG
SAFE RENDER / 1024 × 1024SVG → PNG
PELICAN SCORE
75/ 100

The pelican has mastered the handlebars but is still negotiating terms with the pedals.

A clearly recognizable pelican with a strong bill and pouch sits on a readable bicycle, but the riding relationship is weakened by vague saddle support and unclear foot-pedal contact.

Machine 18/20Vision 57/80

Generated by Kimi 3.1 proModel information is self-reported.

THE REASONING

The bird, the bike, the details.

86% JUDGE CONFIDENCE

Pelican

12 / 15

Clear pelican identity: long orange bill with large throat pouch, white body, small crest, wing extended forward. Neck/body/wing attachment is coherent; legs are thin and oddly placed but readable.

Bicycle

12 / 15

Two spoked wheels, red frame, fork, handlebars and saddle area are recognizable. Crank/pedal region is vague and merged with the feet; drivetrain absent.

Riding

15.5 / 25

Body sits above the frame and wing reaches the handlebar, but there is no clear saddle support and the feet merge into a vague crank area rather than showing convincing pedal contact.

Mechanics

9.5 / 15

Wheels, frame and fork connect plausibly, but the crank/drivetrain is too vague to assess and the fork/steering geometry is simplified; no readable drive path.

Composition

8 / 10

Complete subject with clear silhouettes against a simple beach backdrop; minor tangency where legs and feet merge with the frame/crank area.

SVG quality

18 / 20

Deterministic checks of file health, visible pixels, composition bounds, and structural complexity.

Judge flags: Saddle contact obscured by body · Crank/drivetrain vague · Second foot ambiguous · Wing-handlebar contact slightly merged · No clear saddle support under body · Feet merge into vague crank area · Pedal contact not clearly visible · Drivetrain absent · Fork/steering geometry simplified

Technical SVG checks +
SVG parse validWell-formed SVG XML.2/2
Sanitize successfulStatic SVG allowlist applied.2/2
Render successfulRendered at 1024 × 1024 on white.3/3
Meaningful pixelsVisible content detected.3/3
Content inside viewportPixel-edge heuristic; clipped invisible geometry cannot be fully inferred.2/2
Canvas utilizationVisible bounding box relative to canvas.2/2
Structural complexityElement and path budgets checked.2/2
No prohibited content5 unsafe or unsupported items removed.0/2
Technical SVG qualityNon-empty output and reasonable canvas proportions.2/2
Scoring version
pelican-v1
Judge
deepseek / deepseek-flash
Prompt
pelican-judge-v2
Judge runs
2
Renderer
resvg 2.6.2
SVG pipeline
static-svg-v2-local-use
Submitted (UTC)
2026-11-01 17:29

An experimental score, not a scientific verdict. Understand the limitations ↗