VerifyAI iOS Native SDK

Add AI-powered photo verification to your iOS app with a Swift-first API. On-device CoreML inference, SwiftUI camera overlay, and full offline support.

Quick Start

1. Install

swift
// Package.swift
dependencies: [
  .package(url: "https://github.com/switchlabs/verify-ai-ios", from: "1.0.0")
]

// Or via CocoaPods:
pod 'VerifyAI', '~> 1.0'

2. Use

swift
import VerifyAI

let client = VerifyAIClient(apiKey: "vi_live_...")

// Present the verification scanner
let result = try await client.presentScanner(
  policy: .scooterParking,
  metadata: ["trip_id": "TR-1234"]
)

switch result.outcome {
case .compliant:
  print("Verified: \(result.verificationId)")
case .nonCompliant(let violations):
  print("Issue: \(violations.first?.description ?? "")")
case .error(let error):
  print("Error: \(error)")
}

Features

Swift-First API

Async/await, Result types, Codable models — idiomatic Swift that feels at home in modern iOS apps. No bridging headers required.

CoreML On-Device

AI inference runs on Apple Silicon Neural Engine. Sub-200ms latency on modern devices, with no network round-trip.

SwiftUI + UIKit

Drop-in SwiftUI view (VerifyAIScanner) and UIKit view controller. Use whichever fits your codebase.

Camera Permissions Handled

Permission prompts, denied-state UX, and recovery paths handled out of the box. You don't have to rebuild this every project.

Offline Queue

Verifications queue locally when offline and sync automatically. Your users never lose work when the network drops.

Privacy First

Quality checks and on-device inference happen entirely locally. Only validated, user-approved images are uploaded.

Code Examples

Requirements

  • iOS 14.0 or later
  • Xcode 14 or later
  • Swift 5.7 or later
  • Camera permission (NSCameraUsageDescription in Info.plist)
  • VerifyAI API key (free sandbox available)

Frequently Asked Questions

Ship Photo Verification on iOS

Native Swift, CoreML-powered, production-ready. Start your free sandbox today.

Get in Touch

Questions about pricing, integrations, or custom deployments? We'd love to hear from you.